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 Wed, 23 Nov 2005 17:04:53 GMT
Army wrote:

> Rick Hillegas wrote:
> 
>> Dan Debrunner wrote:
>>
>>> I think I see a similar problem with the upcoming XML changes. If we
>>> return XML as CLOB in jdk 1.4 then applications will break when then
>>> switch to the jdk that supports JDBC 4.0. Again for the same reason,
>>> with jdk 1.4 getObject would return java.sql.Clob and in the JDBC 4.0
>>> jdk it would return java.sql.SQLXML. I think for this case
>>> get/setObject() should not succeed for XML columns until JDBC 4.0 is
>>> supported.
>>>  
>>>
>> Agreed.
> 
> 
> Okay, sounds good.  Then what should we return for the metadata "class
> name"? Esp. ResultSetMetaData.getColumnClassName()?
> 
> The API for that method says:
> 
> "Returns the fully-qualified name of the Java class whose instances are
> manufactured if the method ResultSet.getObject  is called to retrieve a
> value from the column."
> 
> So should a call to that method fail, too?

How about "java.sql.SQLXML" ?

Dan.


Mime
View raw message