Re: storing true/false, was: Comments on adding more
От | Dave Cramer |
---|---|
Тема | Re: storing true/false, was: Comments on adding more |
Дата | |
Msg-id | 1075915033.1712.72.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | storing true/false, was: Comments on adding more connection URL parameters. ("scott.marlowe" <scott.marlowe@ihs.com>) |
Ответы |
Re: storing true/false, was: Comments on adding more connection
|
Список | 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
В списке pgsql-jdbc по дате отправления: