StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19498918
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-10-21T15:40:22.723
FavoriteCount
0
LastActivityDate
2013-10-21T15:49:42.157
LastEditDate
2013-10-21T15:49:42.157
LastEditorUserId
15788
OwnerUserId
15788
ParentId
12884984
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Since the characters <code>/([{;,=!|&~^<>+-*%?:}</code> can't be followed by a division sign, this is what I came up with: <code><searchPattern><![CDATA[/\s+/\e+\\/]]></searchPattern></code> (this one must have at least one whitespace character to avoid conflicts with end-of-line comments) <code><searchPattern><![CDATA[(\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[[\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[{\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[;\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[,\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[=\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[!\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[|\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[&\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[~\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[^\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[<\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[>\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[+\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[-\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[*\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[%\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[?\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[:\s*/\e+\\/]]></searchPattern></code> <code><searchPattern><![CDATA[}\s*/\e+\\/]]></searchPattern></code> For scenarios like <code>if (x) /foo/.exec('bar')</code>, just put the RegExp in parenthesis to format it properly. The only other ill effect is that the preceding character will just be formatted as regular text (not bold or colored).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to fix DreamWeaver's comment highlighting for javascript?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAndy
UserOwnerUserId
1. USAndy
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. COI discovered another problem with this option. Something like ";/*comment*/" is formatted like a regexp.
 singulars
 PostPostId
 PO
 UserUserId
 USAndy

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.