Re: The BOOLEAN data type
From: Paul <paul_at_not.a.chance.ie>
Date: Mon, 7 Apr 2003 14:32:38 +0100
Message-ID: <MPG.18fb8e4ebd65fc0f9896bc_at_news1.eircom.net>
Date: Mon, 7 Apr 2003 14:32:38 +0100
Message-ID: <MPG.18fb8e4ebd65fc0f9896bc_at_news1.eircom.net>
71062.1056_at_compuserve.com says...
> >>I'm working on a project where we store people's gender - what's
> >> wrong with using a boolean for that?
> There is an ISO Standard code for gender and you should use Standards
> whenever they exists.
> 0= unknown
> 1= male
> 2= female
> 9= N/A, lawful person such as a church, school, corporation
When you're doing a system for Youth Hostel memberships, 1 and 2 are all you'll really need!
> Gender is not a flag; it is an attribute. A flag reports a state, an
> attribute takes a value.
OK then, what about Table Billing(blah...., Paid BOOLEAN NOT NULL, blah...)
Is this not a valid use of a Boolean field?
Paul...
-- plinehan__AT__yahoo_DOT_comReceived on Mon Apr 07 2003 - 15:32:38 CEST