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: Not forgiving non-portable applications - Was: Re: behavior of Statement.getGeneratedKeys()
Date Fri, 14 Jul 2006 18:44:08 GMT


Daniel John Debrunner wrote:
> Lance J. Andersen wrote:
>
>   
>>> With 1501 the JDBC spec says the type must be known (I think it's a bug
>>> in the *draft* spec for the type to be ignored), that's the portable
>>> behaviour, ignoring the type not only leads to non-portable applications
>>> but also inconsistencies in derby. E.g. a NULL defined as a DATE could
>>> used for a BLOB value through JDBC, but not using SQL.
>>>   
>>>       
>> Can u help me here as to what it the bug you are referring to?  too many
>> emails today to see the forest through the trees.
>>     
>
> DERBY-1501
>
> http://issues.apache.org/jira/browse/DERBY-1501
>
> You're already on the case. :-)
>   
Well that is good to know... 8-)
> Dan.
>
>   

Mime
View raw message