Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Assuming that you've parsed the configuration file to get a list of extensions and ignored directories, you can build the regular expression as a string and then use the <code>qr</code> operator to compile it into a regular expression:</p> <pre><code>my @extensions = qw(avi flv mp3 mp4 wmv); # parsed from file my $pattern = '\.(' . join('|', @wanted) . ')$'; my $regex = qr/$pattern/; if ($file =~ $regex) { # do something } </code></pre> <p>The compilation isn't strictly necessary; you can use the string pattern directly:</p> <pre><code>if ($file =~ /$pattern/) { # do something } </code></pre> <p>Directories are a little harder because you have two different situations: full names and suffixes. Your configuration file will have to use different keys to make it clear which is which. e.g. "dir_name" and "dir_suffix." For full names I'd just build a hash:</p> <pre><code>%ignore = ('.svn' =&gt; 1); </code></pre> <p>Suffixed directories can be done the same way as file extensions:</p> <pre><code>my $dir_pattern = '(?:' . join('|', map {quotemeta} @dir_suffix), ')$'; my $dir_regex = qr/$dir_pattern/; </code></pre> <p>You could even build the patterns into anonymous subroutines to avoid referencing global variables:</p> <pre><code>my $file_filter = sub { $_ =~ $regex }; my $descend_filter = sub { ! $ignore{$File::Next::dir} &amp;&amp; ! $File::Next::dir =~ $dir_regex; }; my $iter = File::Next::files({ file_filter =&gt; $file_filter, descend_filter =&gt; $descend_filter, }, $directory); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow do I build Perl regular expressions dynamically?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMichael Carman
    1. USMichael Carman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. COWhat I didn't explained was that I will have clients modifying the configuration file. I can't assume they will know Perl or know enough to not introduce a syntax error into the regular expression. So I really don't want to read a regular expression from the configuration file, I just want to a list of file extensions and directory names and/or directory patterns. Example: ext = avi ext = flv ext = mp3 dir = .svn dirp= .frames Once this information is read, then I want to dynamically create something that will function like: .(avi|flv|mp3|mp4|wmv)$
      singulars
      1. PO
      1. USDr. Faust
    2. COAh, that wasn't clear to me before. I've revised my answer.
      singulars
      1. PO
      1. USMichael Carman
 

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