Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 53B32633BCB for ; Mon, 6 Jul 2009 22:23:02 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 68163-07 for ; Mon, 6 Jul 2009 22:22:59 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from wyattearp.actuate.com (mx1.actuate.com [69.1.81.237]) by mail.postgresql.org (Postfix) with SMTP id 27865633BF6 for ; Mon, 6 Jul 2009 22:22:58 -0300 (ADT) Received: from exchange8.actuate.com (Not Verified[192.168.11.22]) by wyattearp.actuate.com with MailMarshal (v6, 1, 4, 441) id ; Mon, 06 Jul 2009 18:22:40 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9FEA1.6B81DAD1" x-cr-puzzleid: {A3299776-3914-40AF-BBD6-DCDF89236C95} x-cr-hashedpuzzle: AHJC BCsO Bj1r CTZF CTpW DFn0 ECit E2Br E3n4 GXIv Gv5v HAUf HEbi HQEi IECv I0/S; 1; cABnAHMAcQBsAC0AcwBxAGwAQABwAG8AcwB0AGcAcgBlAHMAcQBsAC4AbwByAGcA; Sosha1_v1; 7; {A3299776-3914-40AF-BBD6-DCDF89236C95}; cABoAGUAYQBkAGwAYQBuAGQAQABhAGMAdAB1AGEAdABlAC4AYwBvAG0A; Tue, 07 Jul 2009 01:22:50 GMT; QgBlAHMAdAAgAHcAYQB5ACAAdABvACAAcwBpAG0AdQBsAGEAdABlACAAQgBvAG8AbABlAGEAbgBzAA== Content-class: urn:content-classes:message Subject: Best way to simulate Booleans Date: Mon, 6 Jul 2009 18:22:50 -0700 Message-ID: <71F491F5DA99604A80DE49424BF3D02B0C089039@exchange8.actuate.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Best way to simulate Booleans Thread-Index: Acn+oXFCg9tCM02zR820118jD/CMMw== From: "Peter Headland" To: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200907/24 X-Sequence-Number: 32765 This is a multi-part message in MIME format. ------_=_NextPart_001_01C9FEA1.6B81DAD1 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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. God I hate Oracle... --=20 Peter Headland Architect - e.Reports Actuate Corporation ------_=_NextPart_001_01C9FEA1.6B81DAD1 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Best way to simulate Booleans

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.

<VENT>God I hate = Oracle…</VENT>

--

Peter = Headland

Architect - = e.Reports

Actuate Corporation

------_=_NextPart_001_01C9FEA1.6B81DAD1--