Re: storing true/false, was: Comments on adding more

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(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: Re: storing true/false, was: Comments on adding more
Date: 2004-02-04 17:17:14
Message-ID: 1075915033.1712.72.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Scott,

This is a backend thing, 'f' 't' are boolean values for the backend, we
don't attempt to parse and change things.

Dave
On Wed, 2004-02-04 at 11:36, scott.marlowe wrote:
> 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);
>
--
Dave Cramer
519 939 0336
ICQ # 14675561

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message scott.marlowe 2004-02-04 17:20:14 Re: storing true/false, was: Comments on adding more connection
Previous Message Barry Lind 2004-02-04 16:40:12 Re: Comments on adding more connection URL parameters.