storing true/false, was: Comments on adding more connection URL parameters.

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: Kris Jurka <books(at)ejurka(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, <g(dot)tomassoni(at)libero(dot)it>
Subject: storing true/false, was: Comments on adding more connection URL parameters.
Date: 2004-02-04 16:36:36
Message-ID: Pine.LNX.4.33.0402040933420.28468-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On 3 Feb 2004, Dave Cramer wrote:

> Kris,
>
> I also have a few more,
>
> one to change the behaviour for handling booleans, from inserting 't',
> 'f' to inserting '1', and '0'
>
> I think one way to deal with this on a non-connection basis is to use
> System properties, this won't work for the schema search path, but would
> work for most others.
>
> How do the other drivers handle this?

Why not store TRUE and FALSE with no ticks. Like DEFAULT and NULL they're
keywords that mean the exact thing, not an internal representation that
might change over time.

insert into table1 (tf) values (TRUE);

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Barry Lind 2004-02-04 16:40:12 Re: Comments on adding more connection URL parameters.
Previous Message Oliver Jowett 2004-02-04 10:46:35 Re: metadata searching