rolls the dice, hoping for a successful SEDE refresh tomorrow

@JeffSchaller @rene Doesn't seem to have. It says it was updated a couple minutes ago, but I re-ran the query we were discussing above and it returned the same result, including several questions that were later deleted. (I pushed for the deletion of many of the Stack Overflow questions in the list; they're all still in the list.)

@SonictheStay-HomeHedgehog it is still in the middle of the refresh: data.stackexchange.com/stackoverflow/query/1239509

@JeffSchaller fully synced at 10:20 UTC (see above query)

Hurray! :)

@rene it'd be neat to add the current UTC time to that query, to save one click or mental calculation of "is the most recent update close to the current time?"

That ... might still confuse you. SEDE query results are cached once they have run ... and there isn't an "no hands on" way to prune the cache.

added that info

good point about the caching, but if the create_dates haven't changed, and "now" is "sufficiently" beyond the "latest date", we're probably good. Was wondering about hard-coding in a predictor, based on recent average times each site took.

yeah, I might add some more info and then proper name it

@JeffSchaller I've done what I could data.stackexchange.com/stackoverflow/query/1239509 now it is worth mentioning that on a refresh there first is _temp database created and then the new data is loaded, that takes for SO a couple of hours. At the end of that process the actual db is dropped and the _temp one is renamed. I have no way yet to know when the restore finished.

Wow! Impressive SQL work there, rene!

@rene Figured I'd remind you

@SonictheStay-HomeHedgehog that query is updated, it barely runs but after two or three times most data seems to be in-memory so it will just make it in under 2 minutes

@Feeds I've close voted for now. it is unclear what the problem is.

@rene Thanks for the updated query!

The thing I was referring to in the "reminder" above, though, was the message it was a reply to: to update the schema with the new license fields.

I also did that