Re: Booleans - Why in Postgres and not in Oracle or Mysql?

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: CSN <cool_screen_name90001(at)yahoo(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Booleans - Why in Postgres and not in Oracle or Mysql?
Date: 2005-05-09 14:00:47
Message-ID: 1115647247.24459.139.camel@camel
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 2005-05-05 at 15:28, CSN wrote:
>
> --- Dann Corbit <DCorbit(at)connx(dot)com> wrote:
> > > why do you suppose
> > > neither Mysql nor Oracle has bothered to implement
> > it?
> >
> > Probably they just create a domain using a char
> > which can take on two
> > values (e.g. 't'/'f' or 1/0). Oracle 10 has a bit
> > data type (which is a
> > boolean for all intents and purposes):
>
> Could a bit handle NULL's though?
>

ISTR there is some debate on whether Booleans should allow NULL and
thats why the boolean type is still in the extended set of sql spec and
not core.

Inceidentally MySQL's boolean is really scary... it's not just than 0 =
false and 1 = true, its 0 = false and (n >= 1) is true. IMHO that
sounds like a recipe for creating subtle bugs.

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

In response to

Browse pgsql-general by date

  From Date Subject
Next Message AL ELK 2005-05-09 14:05:25 Re: diff value retuns, debug mode and play mode
Previous Message JM 2005-05-09 13:55:22 Need input on postgres used for phpBB