StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20257461
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-11-28T04:01:16.930
FavoriteCount
0
LastActivityDate
2013-11-28T04:01:16.930
LastEditDate
LastEditorUserId
0
OwnerUserId
460557
ParentId
20257085
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
As I said on the comments: you should have a table with all days and left join with your interval and use a SUM instead COUNT. The count only bring results for those that exists in your table. Say that your interval is from <code>2013-01-01 to 2013-01-10</code> and you have theese registries: <pre><code>Created 2013-01-01, 2013-01-01, 2013-01-02, 2013-01-03 </code></pre> it will result in: <code>2, 1, 1</code> there is no way for the sql to know that should exist <code>01-04, 01-05, 01-06... 01-10</code> So you have to create the data of the days and left join with your table. Something like this: Some data example: <pre><code>create table tbl_users( created date ); insert into tbl_users values ( '2013-11-24' ), ( '2013-11-24' ), ( '2013-11-25' ), ( '2013-11-25' ), ( '2013-11-25' ), ( '2013-11-26' ), ( '2013-11-27' ), ( '2013-11-27' ), ( '2013-11-27' ), ( '2013-11-28' ), ( '2013-11-29' ); create table alldays ( dateday date ); --this is just an example to fit the result for today: 2013-11-28 --this table should have all days for the year insert into alldays values ( '2013-11-23' ), ( '2013-11-24' ), ( '2013-11-25' ), ( '2013-11-26' ), ( '2013-11-27' ), ( '2013-11-28' ), ( '2013-11-29' ), ( '2013-11-30' ), ( '2013-12-01' ), ( '2013-12-02' ), ( '2013-12-03' ); </code></pre> Your query should be: <pre><code> SELECT a.dateday, sum( if(b.created is null, 0, 1) ) FROM alldays a left join tbl_users b on (a.dateday=b.created) WHERE a.dateday >= date_sub(curdate(), INTERVAL 7 DAY) AND a.dateday <= NOW() GROUP BY a.dateday </code></pre> See it here: <a href="http://sqlfiddle.com/#!2/cee122/7" rel="nofollow">http://sqlfiddle.com/#!2/cee122/7</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POReturning 0 or NULL on MySQL Interval query
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJorge Campos
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
CommentsPostId
1. CO+1 upvote on you answer!
 singulars
 PostPostId
 PO
 UserUserId
 USJason Heo

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.