"Time" "zones"
-
Just found this in our database:
TimeZoneID TimeZone 1 Central 1 Northeast 1 Southeast 1 West/Midwest 2 Central 2 Northeast 2 West/Midwest 3 West/Midwest 4 West/Midwest
You'll notice that the "TimeZone" column contains values that are...........not time zones.
So I was going to check what TimeZoneID links to, to see if it's more accurate.
What is links to? Nothing. It's an integer column that references nothing.
-
So… no uniqueness constraints on either column. Might as well label
TimeZoneID
asPeoniePopsFavoriteNumber
.
-
You'll notice that the "TimeZone" column contains values that are...........not time zones.
So I was going to check what TimeZoneID links to, to see if it's more accurate.
What is links to? Nothing. It's an integer column that references nothing.
Does anything reference this table to begin with? It looks like an abortion that needs to be bludgeoned to death with a Codd.
-
Yes, it's used extensively, although these columns are not. I think they're mostly used in the change that went to prod last night that is causing the commotion that my co-worker is dealing with right now.
-
Those columns are far safer dropped entirely than someone accidentally using them. Timezones are dastardly things with lots of legal surrounding them, and this probably violates everything from human rights to legal rights.
Hi read only forum mode.
-
-
At least renamed to "Region" and "WTF_ID"
-
My fault.
Fun fact - I had it for an hour or so yesterday, but there were absolutely zero problems with posting.
Filed under: at least zero new problems
-
Fun fact - I had it for an hour or so yesterday, but there were absolutely zero problems with posting.
Probably something in the browser that needed a hard refresh.
I normally do that sort of thing early UTC before the Eastern Seaboard fully wakes up - left it a bit late yesterday.
-
So the "fix" that they were going to use was to add the Time Zone to the State lookup table.
I put a stop to that pretty quickly...