StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3828291
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-09-30T06:28:26.403
FavoriteCount
0
LastActivityDate
2010-09-30T06:36:14.157
LastEditDate
2010-09-30T06:36:14.157
LastEditorUserId
20670
OwnerUserId
20670
ParentId
3827462
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<pre><code>(?<=#if DEBUG(?:(?!#endif\b).)*)Logging\.Log[^\r\n]*(?=.*#endif) </code></pre> will match <code>Logging.Log</code> and whatever else follows on that line only if it's between <code>#if DEBUG</code> and <code>#endif</code>. Note that you need to use <code>RegexOptions.Singleline</code> for this to work. This regex relies on a feature that only few regex engines have, namely infinite repetition inside <a href="http://www.regular-expressions.info/lookaround.html" rel="nofollow">lookbehind assertions</a>. Fortunately, .NET is among those. In C#: <pre><code>StringCollection resultList = new StringCollection(); Regex regexObj = new Regex(@"(?<=#if DEBUG(?:(?!#endif\b).)*)Logging\.Log[^\r\n]*(?=.*#endif)", RegexOptions.Singleline); Match matchResult = regexObj.Match(subjectString); while (matchResult.Success) { resultList.Add(matchResult.Value); matchResult = matchResult.NextMatch(); } </code></pre> Explanation: <pre><code># from the current position, look behind in the string to check... (?<= # whether it is possible to match... #if DEBUG # the literal text # if DEBUG (?: # followed by... (?!#endif\b) # (as long as we can't match #endif along the way) . # any character )* # any number of times ) # end of lookbehind assertion. Logging\.Log # Then match Logging.Log, [^\r\n]* # followed by any character(s) except newlines. (?= # as long as there is (further up ahead)... .*#endif # any number of characters, followed by #endif ) # end of lookahead </code></pre> If you're sure that every <code>#if DEBUG</code> ends with an <code>#endif</code>, then you can drop the <code>(?=.*#endif)</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POregex to pull out strings inside #if debug #endif block
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTim Pietzcker
UserOwnerUserId
1. USTim Pietzcker
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
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.