I wrote:
> > The latest JDBC driver (build 213) returns -7 for
> > the java.sql.Types value (obtained via DBMetaData,
> > getColumns() and then "DATA_TYPE"). I am not sure
> > if this has been a bug with all postgres JDBC
> drivers
> > or if this is some kinda regression bug.
> >
> > -7 corresponds to a java.sql.Types.BIT and should
> > NOT be returned for a BOOLEAN type.
> >
> > For a BOOLEAN type, a value of 16 should be
> returned
> > which corresponds to a java.sql.Types.BOOLEAN.
Oliver wrote:
> 1) BOOLEAN exists only in JDBC3. What should the
> driver return for a
> boolean column if JDBC1 or JDBC2 is in use?
Hmm. I see. Maybe fallback to BIT for those and
return BOOLEAN it usinng JDBC3 ? But that may be
more trouble than it's worth.
> 2) JDBC3 explicitly says that either BOOLEAN or BIT
> may be returned for
> a boolean data type. See the tables in appendix B of
> the specificaton
> (pg. 175-180).
Ok. Thanks for pointing this out.
> 3) JDBC3 also says that "BOOLEAN is logically
> equivalent to BIT" (pg. 22).
Ok. Leave things the way they are. This is no big
deal in hindsight. In my database abstraction layer,
I have arranged to generate a 'getBoolean(..) method
for both BIT and BOOLEAN column types.
Best regards,
--j
__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html
