(almost) time for that biannual DST rant

Mar 10, 2013 00:00

So what would happen if a deviant freak like me wrote the time on a marriage certificate to be at 2:30am today*? Of course it cannot be filed because courts are closed, but drop it off on Monday and see if you can find a dull-witted sleep-deprived clerk to enter it into evidence. At some time it will be entered into a computer, which will happily ( Read more... )

Leave a comment

Comments 4

fub March 10 2013, 08:28:27 UTC
I strongly suspect there is no DST-logic built into the applications that serve to record such matters as marriages. If that is the case, it'll go through unharmed.

Reply

merle_ March 10 2013, 08:46:00 UTC
I'm assuming it relies on the DBMS to deal with it, and rather than store it in separate date and time fields it would store it in a single datetime -- which would likely be a numeric for >= comparisons? It's an assumption, though. Having stored them separately for a calendar app I can tell you it was a mess to convert in JavaScript.

Reply


q_pheevr March 10 2013, 13:45:57 UTC

Do marriage certificates (or marriage licences) even have a field for the time? I don't really see why they would need anything more precise than the date.

My birth certificate, on the other hand, does record the time, to the minute. I'm glad it's not one of those phantom hours; I would hate to have my birth annulled.

Reply

merle_ March 10 2013, 18:37:33 UTC
Huh. Sure enough, google suggests only the date is required. Foiled again!

And not to worry, if your birth is annulled there is probably legal precedent for retroactive abortion, so the culprit will hang from the highest tree. Or spend the rest of their life making license plates.

Reply


Leave a comment

Up