db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance J. Andersen" <Lance.Ander...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-695) Re-enable the TINYINT datatype
Date Fri, 11 Nov 2005 20:52:21 GMT


Daniel John Debrunner wrote:

>Lance J. Andersen wrote:
>
>  
>
>>>Hmmmm, that's kind of an awkward place to be in. It seems you want to
>>>add this non-standard SQL type to match other databases, but by matching
>>>the other databases you break the JDBC spec. :-)
>>> 
>>>
>>>      
>>>
>>I do not see how this is going to break anything.  The JDBC spec
>>indicates should, not  "must".
>>
>>    
>>
>
>  
>
>>So i guess i am not sure of your concern dan.  This datatype has worked
>>fine for drivers which have supported Sybase and MS SQL server for years.
>>    
>>
>
>Maybe break was too strong, how about 'has the potential to confuse
>application developers'. :-)
>
>Just looking at the various tables in appendix B, the natural choice for
>an application developer to use is byte, setByte, getByte. Given the
>mappings in B1 & B2, and the big X in the getByte-TINYINT cell of B-6.
>  
>
Understand but this is also somewhat of a guide as not every database 
supports the datatypes listed in the list so it is not just a straight 
answer.

JDBC is really just plumbing so unfortunately the user has to know the 
requirements of the backend.

>Thus they may find their application works fine, because they only test
>it with values in the range 0-128, but later hit bugs in the field when
>larger values are used.
>  
>
True, but this is not the only scenario where this could happen due to 
database compatiblity issues

>If the JDBC TINYINT type was really put there to match the TINYINT SQL
>datatype of SQL Server and Sybase, then maybe JDBC 4.0 should clarify
>this so that the type mapping in B1 and B2 is TINYINT <-> short and B6
>has the big X in getShort-TINYINT cell?
>  
>
I will put this on my todo list to have the fun EG discussion, but i am 
afraid this will open up pandoras box  about all data types that are not 
explictly supported.


>Dan.
>
>
>
>
>  
>

Mime
View raw message