StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17547950
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-07-09T12:16:25.973
FavoriteCount
0
LastActivityDate
2013-07-09T12:21:52.137
LastEditDate
2013-07-09T12:21:52.137
LastEditorUserId
655699
OwnerUserId
655699
ParentId
17547290
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
is you use different formats for the string then you can avoid this behaviour. There are 2 iso formats that are always specific -- sql server will always parse them in the same way regardless of the server date format setting. These are: 1) Short form : YYYYMMDD. Example '20120301' -- 1st March 2012 2) Long Form : YYYY-MM-DDTHH:MM:SS.msms'. Example '2012-03-01T12:13:00.000Z' -- 1st March 2012 at 13 minutes past 12 (PM) In the long form the miliseconds is optional -- this is a perfectly acceptable ISO datetime '2012-03-01T12:13:00Z' The Z at the end is time zone information. SQL Server doesn't actually require this. (though other products are a bit more exacting) Try this for example: <pre><code>DECLARE @foo DATETIME SET DATEFORMAT DMY -- this will be the 3rd of january in DMY SET @foo = '2012-03-01' SELECT 'DMY: Not ISO', @foo SET @foo = '20120301' SELECT 'DMY: ISO', @foo SET DATEFORMAT MDY -- this will be the 1st of March in MDY SET @foo = '2012-03-01' SELECT 'MDY: not ISO', @foo SET @foo = '20120301' SELECT 'MDY: ISO', @foo </code></pre> When you use text to enter dates you should always try to use one of the two ISO standards. It just makes things much more deterministic. Short format (SQL Server) <a href="http://msdn.microsoft.com/en-US/library/ms187085(v=sql.90).aspx" rel="nofollow">http://msdn.microsoft.com/en-US/library/ms187085(v=sql.90).aspx</a> ISO 8601 Format (SQL Server) <a href="http://msdn.microsoft.com/en-us/library/ms190977(v=sql.90).aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms190977(v=sql.90).aspx</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSQL Server date formatting from string
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTransact Charlie
UserOwnerUserId
1. USTransact Charlie
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CO+1 - for the good answer.
 singulars
 PostPostId
 PO
 UserUserId
 USDevart

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.