Dabblingwithdata.wordpress.com Website Review

extracting the date and time a uuid was created with bigquery sql (with a brief foray into the history of the gregorian calendar) i was recently working with records in a database that were identified by a universally unique identifier, aka a uuid i needed to know which records were generated during in a particular time period, but sadly there was no field about dates to be found. unambiguously a database design flaw given what i needed to do – but it did lead me to discover that at least “version 1 uuids so how do we get from 31ae75f0-cbe0-11e8-b568-0800200c9a66 to the date and time the uuid was generated? i’d say “simple”, but it so, the key components of the uuid to note by position are those highlighted below: take the highlighted parts of the uuid aside, reversing the order of the chunks, so as to get: there’s your “60-bit timestamp, being the number of 100-nanosecond intervals since midnight 15 october 1582” (thanks in case you’re wondering why 15 october 1582 is so special, then it’s because that was the date that the previous “julian why? the julian calendar had worked on the premise that the average year is 365.25 days long (the 0.25 days being compensated for by the however, that’s slightly different to the true length of the solar year, which is 365 days, 5 hours, 48 minutes, 45.25 seconds calendar noted that the equinoxes should occur slowly became out of sync with real life observations of the equinox. effectively, as the regress almost one day per century”. this is relevant to religions such as catholicism in that it affects the calculation of, for the gregorian calendar made a couple of changes, perhaps most notably introducing the rule that a century year (e.g. 1900) only counts as a leap year if its number is divisible by 400 with no remainder, instead of adhering to the julian system where it only needs to be divisible by 4.  on average, this shortens the length of the measured year by  0.0075 days, which keeps it in better sync with the reality of