Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

The Data Explorer claims that the most recent data is from Dec 7th thru 13th, for all sites.

Last SEDE update

But, it was pointed out to me that this query returns an invalid row (NullUserException earned the badge as of Nov. 15th).

So then I made this query and it claims that NullUserException only has 107 badges, with the latest earned on Nov. 12th.

However, NullUserException actually has 115 badges -- all of them earned well before this latest SEDE update!

So what went wrong with the SEDE data? And, how can we make sure that it won't happen again?


As Conrad Frix points out, none of the data in SO appears to be updated!

I verified this with this query. Indeed, the query on several  other  sites, shows that apparently no data in the SEDE is newer than Nov 13th.

The "most recent" date displays are lies "suboptimal"!

share|improve this question
If you run ​SELECT max(date) , (SELECT max(creationdate) FROM posts), (SELECT max(creationdate) FROM users) FROM badges everything comes up with 11/13/2011 which probably indicates that the Data.SE home Page is a liar ​ – Some Helpful Commenter Dec 14 '11 at 22:49
Good point, @ConradFrix. I've updated the question. – Awesome Poodles Dec 14 '11 at 23:51
Methinks "most recent" refers to the last time SEDE has been updated. – NullUserException อ_อ Dec 15 '11 at 0:11
By the way, have you seen – NullUserException อ_อ Dec 15 '11 at 0:14
@NullUserExceptionอ_อ: Pretty sure that the displays are meant for when the data is updated. A couple of days ago, these displays were all "nov 13" (as was the latest data) and the data is supposed to be updated monthly. Also, in some post (which I will try to dig up), it's claimed that these dates are for data. Finally, the SEDE code was apparently last updated on Dec. 8th. – Awesome Poodles Dec 15 '11 at 0:21
Thanks for catching this. As pointed out, part of the system thinks it was updated in December, and the other part thinks it is still from November. Looking into it... – Rebecca Chernoff Dec 15 '11 at 1:41
up vote 2 down vote accepted

I believe this has been resolved - I'd appreciate any testing you can do to make sure this is working properly.

share|improve this answer
Thanks! What was the issue and how will it not recur? – Awesome Poodles Dec 15 '11 at 21:01
Well, it looks like the data has been updated for all the sites (spot checked over 20). But, there are slight discrepancies. EG, SEDE claims that The cooking site's "most recent" data is Dec 13, but it is actually Dec 14. – Awesome Poodles Dec 15 '11 at 21:01
Do all of the datetime columns have indices? As I build up the query, it slows down way more than it should when some relatively small tables are added in. The "Include Execution Plan" option appears to be busted. – Awesome Poodles Dec 15 '11 at 21:49
@BrockAdams I refactored your query here so that it runs – Some Helpful Commenter Dec 19 '11 at 3:17
@ConradFrix, Ah, I see you made up for the appalling lack of indices on the datetime columns by assuming that the last ID is also the latest timestamp. The the ID columns are all indexed, so this performs well. Good workaround. Thanks! – Awesome Poodles Dec 19 '11 at 5:35

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .