db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-695) Re-enable the TINYINT datatype
Date Wed, 09 Nov 2005 23:51:11 GMT

>http://java.sun.com/j2se/1.3/docs/guide/jdbc/getstart/mapping.html
>
>This mapping is reflected in the data returned by DatabaseMetaData.getTypeInfo
>
>On an implementation note, the link above says TINYINT is valued 0-255 signed or unsigned,
I do not believe that is what was implemented by Cloudscape, or any existing code in Derby.
I seem to remember Cloudscape used a Java byte which holds values -128 to 127, thus its a
good thing the TINYINT type was removed/disabled because it was non-standard on several fronts.
>  
>
I'm afraid I don't understand. The above link says that a JDBC TINYINT 
is an 8-bit integer which fits in a byte and may be regarded as signed 
or unsigned. And you say that Cloudscape implemented this as a byte. I'm 
missing the discrepancy here. For the record, Postgres, SQL Server, and 
Sybase all treat TINYINT as an 8-bit integer.

Mime
View raw message