Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As soon as you come across a <code>**</code>, you're going to have to recurse through the whole directory structure, so I think at that point, the easiest method is to iterate through the directory with os.walk, construct a path, and then check if it matches the pattern. You can probably convert to a regex by something like:</p> <pre><code>def glob_to_regex(pat, dirsep=os.sep): dirsep = re.escape(dirsep) print re.escape(pat) regex = (re.escape(pat).replace("\\*\\*"+dirsep,".*") .replace("\\*\\*",".*") .replace("\\*","[^%s]*" % dirsep) .replace("\\?","[^%s]" % dirsep)) return re.compile(regex+"$") </code></pre> <p>(Though note that this isn't that fully featured - it doesn't support <code>[a-z]</code> style glob patterns for instance, though this could probably be added). (The first <code>\*\*/</code> match is to cover cases like <code>\*\*/CVS</code> matching <code>./CVS</code>, as well as having just <code>\*\*</code> to match at the tail.)</p> <p>However, obviously you don't want to recurse through everything below the current dir when not processing a <code>**</code> pattern, so I think you'll need a two-phase approach. I haven't tried implementing the below, and there are probably a few corner cases, but I think it should work:</p> <ol> <li><p>Split the pattern on your directory seperator. ie <code>pat.split('/') -&gt; ['**','CVS','*']</code></p></li> <li><p>Recurse through the directories, and look at the relevant part of the pattern for this level. ie. <code>n levels deep -&gt; look at pat[n]</code>.</p></li> <li><p>If <code>pat[n] == '**'</code> switch to the above strategy:</p> <ul> <li>Reconstruct the pattern with <code>dirsep.join(pat[n:])</code></li> <li>Convert to a regex with <code>glob\_to\_regex()</code></li> <li>Recursively <code>os.walk</code> through the current directory, building up the path relative to the level you started at. If the path matches the regex, yield it.</li> </ul></li> <li><p>If pat doesn't match <code>"**"</code>, and it is the last element in the pattern, then yield all files/dirs matching <code>glob.glob(os.path.join(curpath,pat[n]))</code></p></li> <li><p>If pat doesn't match <code>"**"</code>, and it is NOT the last element in the pattern, then for each directory, check if it matches (with glob) <code>pat[n]</code>. If so, recurse down through it, incrementing depth (so it will look at <code>pat[n+1]</code>)</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POHow would you implement ant-style patternsets in python to select groups of files?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGautam
    1. USBrian
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow would you implement ant-style patternsets in python to select groups of files?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload