db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: [jira] Updated: (DERBY-499) Expose BOOLEAN datatype to end users
Date Tue, 22 Nov 2005 23:29:25 GMT
Rick Hillegas wrote:

> It depends on what rev level you're running at. Here are the cases:
> 
> Embedded on jdk1.3:
> 
>    DatabaseMetaData:  java.sql.Types.BIT (called "BOOLEAN")
>    ResultSetMetaData: java.sql.Types.BIT (called "BOOLEAN")
> 
> Embedded on jdk1.4:
> 
>    DatabaseMetaData:  java.sql.Types.BOOLEAN (called "BOOLEAN")
>    ResultSetMetaData: java.sql.Types.BOOLEAN (called "BOOLEAN")
> 
> Client on jdk1.3/1.4 against server on jdk1.3:
> 
>    DatabaseMetaData:  java.sql.Types.BIT (called "BOOLEAN")
>    ResultSetMetaData: java.sql.Types.SMALLINT (called "SMALLINT")
> 
> Client on jdk1.3/jdk1.4 against server on jdk1.4:
> 
>    DatabaseMetaData:  java.sql.Types.BOOLEAN (called "BOOLEAN")
>    ResultSetMetaData: java.sql.Types.SMALLINT (called "SMALLINT")


> I am trying to avoid an explosion of cases because I think that will
> cause a lot of support headaches. The simplification I was hoping for
> was one set of behaviors governing clients/servers operating at the
> current Derby and JDBC rev level and another set of behaviors for all
> other combinations.

I would have no issue if existing JCC/10.1 network clients continued to
report BOOLEAN as SMALLINT, as they seem to. I would have an issue if
you changed the current correct behaviour of embedded under jdk 1.3 to
match that.

Dan.



Mime
View raw message