Log in

No account? Create an account
23 July 2002 @ 11:23 am
Me: "Woohoo! We have a tri-state boolean field!"
Everybody Else: "Huh?"
Lady Doomlithera on July 23rd, 2002 11:25 am (UTC)
Cool. What're you going to do with it?
St. Sean the Amused: daemonseanb on July 23rd, 2002 11:47 am (UTC)
Provide an alternate way for end-users to connect to our servers if their firewall gives them problems with our primary way.

Lady Doomlithera on July 23rd, 2002 11:48 am (UTC)
*nods* All good. Or well, possibly a pain in the ass per your other answer, but...
Stupendous Manfarmalloc on July 23rd, 2002 11:32 am (UTC)
Um...that is a twad odd...a boolean is a true or false...how have you added the thrid state and for what reason?
St. Sean the Amusedseanb on July 23rd, 2002 11:45 am (UTC)
Our DBM added a boolean field to our Hospitals table to indicate whether an alternate sync server should be used. He did not specify this field as "Not NULL", so the field has three possible states:
0 (false)
1 (true)
NULL (!= 0)

In my logic, I'm setting it up so that a 0 indicates sites explicitly set for the primary server, a 1 indicates sites set for the alternate server, and Nulls indicate sites that predate this distinction (and have to be handled differently).

Ugh. The way he set up this DB, Nulls are allowed almost EVERYWHERE.
Stupendous Manfarmalloc on July 23rd, 2002 12:43 pm (UTC)
I see. That blows much chunks...so you have to sxplictily write stuff to handle all the special cases with nulls. So your DB is not well designed...at least you have one. I have been trying to convince people here that we should create one. It would make my life a whole lot easier and allow alot of interesting correlations they havn't even thought of.