StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODateTime.TryParseExact not working as expected
primarykey
Id
5905728
data
AcceptedAnswerId
0
AnswerCount
5
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2011-05-06T00:52:56.610
FavoriteCount
1
LastActivityDate
2011-05-06T02:14:34.620
LastEditDate
2011-05-06T02:14:34.620
LastEditorUserId
285951
OwnerUserId
285951
ParentId
0
PostTypeId
1
Score
10
ViewCount
14501
LastEditorDisplayName
text
Body
Can anyone explain why the following snippet returns true? According to the docs for <a href="http://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx#dSpecifier">The "d" custom format specifier</a>, "A single-digit day is formatted without a leading zero." So why doesn't TryParseExact fail when I give it a single-digit day with a leading zero? <pre><code>DateTime x; return DateTime.TryParseExact ( "01/01/2001", @"d\/MM\/yyyy", null, System.Globalization.DateTimeStyles.None, out x ); </code></pre> UPDATE I think maybe I was unclear originally. What I am really trying to get at is: Why does TryParseExact accept some values that don't match exactly? from all of the documentation I have seen, 'd' matching '01' and '1' is just as much a bug as if 'MM' matched 'March' as well as '03'. The issue here isn't that the values are equivalent, its that they don't match the format. The relevant snippets of documentation are: <ul> <li>From <a href="http://msdn.microsoft.com/en-us/library/system.datetime.tryparseexact.aspx">TryParseExact</a>: The format of the string representation must match a specified format exactly.</li> <li>From <a href="http://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx#dSpecifier">The 'd' Specifier</a>: A single-digit day is formatted without a leading zero.</li> </ul> It seems abundantly clear to me that '01' has a leading 0, and therefore doesn't exactly match 'd'. 
Tags
<c#><datetime><tryparse>
Title
DateTime.TryParseExact not working as expected
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USverdesmarald
UserOwnerUserId
1. USverdesmarald
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PODateTime.TryParseExact not working as expected
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PODateTime.TryParseExact not working as expected
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PODateTime.TryParseExact not working as expected
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.