db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2430) setObject(int targetType, Blob source) and setObject(int targetType, Clob source) should disallow updates on all targetTypes except BLOB and CLOB respectively
Date Fri, 09 Mar 2007 07:51:24 GMT
 setObject(int targetType, Blob source) and setObject(int targetType, Clob source) should disallow
updates on all targetTypes except BLOB and CLOB respectively
---------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: DERBY-2430
                 URL: https://issues.apache.org/jira/browse/DERBY-2430
             Project: Derby
          Issue Type: Sub-task
          Components: Network Client
         Environment: All
            Reporter: V.Narayanan


updateBlob(int columnIndex, Blob x), updateClob(int columnIndex, Clob x) can be implemented
by forwarding calls to  setObject(int targetType, Blob source), setObject(int targetType,
Clob source). If this this done then

1) updateClob on a CHAR/VARCHAR/LONG VARCHAR column throws an exception on the Embedded Driver
but not on the NetworkClient
2) updateBlob works on a CHAR/VARCHAR/LONG VARCHAR FOR BIT DATA throws an exception on the
Embedded Driver but not on the NetworkClient

>From what the JDBC 4.0 spec says (pg 198 table b-5) the Embedded behaviour seems to be
correct.

This can be fixed by Matching Embedded behaviour. This would involve throwing an exception
in the cases mentioned above



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message