StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8493368
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-12-13T17:21:43.753
FavoriteCount
0
LastActivityDate
2011-12-13T17:21:43.753
LastEditDate
LastEditorUserId
0
OwnerUserId
13508
ParentId
8437148
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
As explained in the manual, <a href="http://es2.php.net/date_create" rel="nofollow">date_create()</a> is an alias for <a href="http://es.php.net/manual/en/datetime.construct.php" rel="nofollow">DateTime::__construct()</a>. And there we can read: <blockquote> Return Values Returns a new DateTime instance. Procedural style returns FALSE on failure. </blockquote> So it's pretty clear where the boolean comes from. Now, your code shows many conversions from Unix timestamp to string and viceversa but not the value you start from, so it's impossible to point out the exact source of the problem. But I'd say you have certain confusion about the data types involved in date handling. Here's a little summary: <ul> <li>Unix timestamp: it's an integer that counts the number of seconds since the Unix Epoch (Jan 1970). It's the value handled by legacy date functions that receive an integer as argument or return one.</li> <li>DateTime: it's the new object-oriented date feature introduced in PHP/5.2.</li> <li>Strings: it's not a standardised format per-se so it should only be used for display purposes or as intermediate format (for instance, to insert a date into a database).</li> </ul> Sadly, the DateTime constructor only accepts strings and does not even allow to tell the exact format (IMHO, a not well-thought design decision). To reduce the potential ambiguity (is <code>10/11/2011</code> 10th Nov. or 11 Oct?), I suggest you use the <code>"YYYY-MM-DD"</code> format. A tip: decide whether to use timestamps or DateTime objects and stick to that. It'll make your live easier.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPHP - Date as Wrong Data Type
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USÁlvaro González
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPHP - Date as Wrong Data Type
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COSo it needed to be in YYYY-MM-DD format...
 singulars
 PostPostId
 PO
 UserUserId
 USDissident Rage

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.