Databases
StackOverflow2013
Postsdbo
PORegex Query Help - Lookbehind
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORegex Query Help - Lookbehind
    primarykey
    data
    text
    <p>This is somewhat related to: <a href="https://stackoverflow.com/questions/15278728/regular-expression-formatting-text-in-a-block-im">Regular Expression - Formatting text in a block - IM</a> but a different problem.</p> <p>Looking for <code>-</code>'s wrapping text with the following conditions:</p> <p>Conditions:</p> <ul> <li>token can be at start or end of line</li> <li>token must be surround by space or one or more symbols: {.,!@#$....}. <ul> <li>must not be a normal character [a-zA-Z] surrounding the <code>-</code> pair in question.</li> <li>See Sample test 3 ...w-thank you-</li> <li>Test 4 and 5 succeed because the <code>-</code> is wrapped with [^a-zA-Z]</li> </ul></li> <li>token must not be followed by a space on the first <code>-</code> or a space preceding the last <code>-</code> <ul> <li>"-Wow -" will not be a match as the closing <code>-</code> was preceded by a space.</li> <li>See Sample test 6 and 7</li> </ul></li> </ul> <p>For the front of the regular expression I would need: <code>(^|[\s\W]+)</code><br /> and the end would be: <code>($|[\s\W]+)</code></p> <p>I have the current expression, but it is failing due to the escape condition being stop after finding the first <code>-</code></p> <pre><code> (^|[\s\W]+)-([^\s][^-]*)-($|[\s\W]+) </code></pre> <p>Sample test strings would be:</p> <ol> <li>(all.): <code>-Wow-thank you-.</code></li> <li>(Wow): <code>-Wow- thank you-!</code></li> <li>(NIL): <code>- Wow-thank you-.</code></li> <li>(thank you): <code>- Wow!-thank you-</code></li> <li>(thank you): <code>- Wow -thank you-</code></li> <li>(all): <code>-Wow - thank you-</code></li> <li>(NIL): <code>-Wow - thank you -</code></li> </ol> <p>Does this require look behind? (I'm a regex newbie so please bear with me) Or is my middle condition totally wrong.</p> <p>Thank you much!<br /> mwolfe.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USMike Wolfe
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORegex Query Help - Lookbehind
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORegex Query Help - Lookbehind
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORegex Query Help - Lookbehind
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't understand your 1st comment after your 2nd condition.
      singulars
      1. PORegex Query Help - Lookbehind
      1. USRohit Jain
    2. COExample 3 fails by this condition because there is a character "w" before the "-thank you-". If that character was a space or a symbol then "-thank you-" would have been identified/flagged/found. That is why Example 4 work because the character before the "-" was a "!"
      singulars
      1. PORegex Query Help - Lookbehind
      1. USMike Wolfe
    3. CO+1 - Very nice attempt, especially for a (self-proclaimed) newbie.
      singulars
      1. PORegex Query Help - Lookbehind
      1. USAndrew Cheong
 

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