From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Peter Headland <pheadland(at)actuate(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Best way to simulate Booleans |
Date: | 2009-07-07 06:13:46 |
Message-ID: | dcc563d10907062313j1f0eb27awc2bea6b3f810dc41@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Mon, Jul 6, 2009 at 7:22 PM, Peter Headland<pheadland(at)actuate(dot)com> wrote:
> I know, I know, PostgreSQL has Booleans that work very nicely.
> Unfortunately, I have to create a schema that will work on Oracle as well as
> PostgreSQL, by which I mean that a single set of Java/JDBC code has to work
> with both databases. I have an XML meta-schema that enables me to generate
> appropriate DDL; that handles all the INTEGER vs. NUMBER(m,n) stuff. But
> Oracle simply has no Booleans, so I will have to resort to some more or less
> ugly alternative. I am hoping that others here have had to deal with this
> and can suggest an approach that will be minimally loathsome.
The most transportable method would be to use either a char(1) or an
int with a check constraint.
mybool char(1) check (mybool in ('t','f'))
mybool int check (mybool >=0 and <=1)
Or something like that.
From | Date | Subject | |
---|---|---|---|
Next Message | Dirk Jagdmann | 2009-07-07 09:05:15 | Re: Best way to simulate Booleans |
Previous Message | Andreas Joseph Krogh | 2009-07-07 02:06:07 | Re: Order of "WITH RECURSIVE" output |