StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2919321
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-05-27T07:47:40.047
FavoriteCount
0
LastActivityDate
2010-05-27T07:47:40.047
LastEditDate
LastEditorUserId
0
OwnerUserId
237428
ParentId
2918082
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
As paxdiablo said, you almost certainly don't want to use a regex here. The <code>split</code> suggestion isn't bad; I myself would probably use a parser here—there's a lot of structure to exploit. The idea here is that you formally specify the syntax of what you have—sort of like what you gave us, only rigorous. So, for instance: a <code>field</code> is a sequence of non-single-quote characters surrounded by single quotes; a <code>fields</code> is any number of <code>field</code>s separated by white space, a <code>|</code>, and more white space; a <code>tilde</code> is non-right-parenthesis characters surrounded by <code>(~</code> and <code>)</code>; and an <code>expr</code> is a <code>fields</code>, optional whitespace, an optional <code>tilde</code>, a <code>=</code>, optional whitespace, and another <code>fields</code>. How you express this depends on the language you are using. In Haskell, for instance, using the Parsec library, you write each of those parsers as follows: <pre><code>import Text.ParserCombinators.Parsec field :: Parser String field = between (char '\'') (char '\'') $ many (noneOf "'\n") tilde :: Parser String tilde = between (string "(~") (char ')') $ many (noneOf ")\n") fields :: Parser [String] fields = field `sepBy` (try $ spaces >> char '|' >> spaces) expr :: Parser ([String],Maybe String,[String]) expr = do left <- fields spaces opt <- optionMaybe tilde spaces >> char '=' >> spaces right <- fields (char '\n' >> return ()) <|> eof return (left, opt, right) </code></pre> Understanding precisely how this code works isn't really important; the basic idea is to break down what you're parsing, express it in formal rules, and build it back up out of the smaller components. And for something like this, it'll be much cleaner than a regex. <hr> If you really want a regex, here you go (barely tested): <pre><code>^\s*('[^']*'((\s*\|\s*)'[^'\n]*')*)?($~[^)\n]*$)?\s*=\s*('[^']*'((\s*\|\s*)'[^'\n]*')*)?\s*$ </code></pre> See why I recommend a parser? When I first wrote this, I got at least two things wrong which I picked up (one per test), and there's probably something else. And I didn't insert capturing groups where you wanted them because I wasn't sure where they'd go. Now yes, I could have made this more readable by inserting comments, etc. And after all, regexen have their uses! However, the point is: this is not one of them. Stick with something better.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I use a regular expression to match something in the form 'stuff=foo' 'stuff' = 'stuff' 'more stuff'
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAntal Spector-Zabusky
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.