Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Contrary to all the answers here, for what you're trying to do regex is a perfectly valid solution. This is because you are NOT trying to match balanced tags-- THAT would be impossible with regex! But you are only matching what's in one tag, and that's perfectly regular.</p> <p>Here's the problem, though. You can't do it with just one regex... you need to do one match to capture an <code>&lt;input&gt;</code> tag, then do further processing on that. Note that this will only work if none of the attribute values have a <code>&gt;</code> character in them, so it's not perfect, but it should suffice for sane inputs.</p> <p>Here's some Perl (pseudo)code to show you what I mean:</p> <pre><code>my $html = readLargeInputFile(); my @input_tags = $html =~ m/ ( &lt;input # Starts with "&lt;input" (?=[^&gt;]*?type="hidden") # Use lookahead to make sure that type="hidden" [^&gt;]+ # Grab the rest of the tag... \/&gt; # ...except for the /&gt;, which is grabbed here )/xgm; # Now each member of @input_tags is something like &lt;input type="hidden" name="SaveRequired" value="False" /&gt; foreach my $input_tag (@input_tags) { my $hash_ref = {}; # Now extract each of the fields one at a time. ($hash_ref-&gt;{"name"}) = $input_tag =~ /name="([^"]*)"/; ($hash_ref-&gt;{"value"}) = $input_tag =~ /value="([^"]*)"/; # Put $hash_ref in a list or something, or otherwise process it } </code></pre> <p>The basic principle here is, don't try to do too much with one regular expression. As you noticed, regular expressions enforce a certain amount of order. So what you need to do instead is to first match the CONTEXT of what you're trying to extract, then do submatching on the data you want.</p> <p><b>EDIT:</b> However, I will agree that in general, using an HTML parser is probably easier and better and you really should consider redesigning your code or re-examining your objectives. :-) But I had to post this answer as a counter to the knee-jerk reaction that parsing any subset of HTML is impossible: HTML and XML are both irregular when you consider the entire specification, but the specification of a tag is decently regular, certainly within the power of PCRE.</p>
    singulars
    1. This table or related slice is empty.
    1. PORegular expression pattern not matching anywhere in string
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPlatinum Azure
    1. USPlatinum Azure
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORegular expression pattern not matching anywhere in string
      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. CONot contrary to *all* the answers here. :)
      singulars
      1. PO
      1. UStchrist
    2. COgreat stuff, i am going to implement this in php, so let me try this
      singulars
      1. PO
      1. USSalman
    3. CO@Salman: PHP is one of the luckier ones, since it uses PCRE. You shouldn’t have any trouble. That said, I do find meder’s solution extremely attractive.
      singulars
      1. PO
      1. UStchrist
 

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