db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (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 Tue, 13 Mar 2007 07:51:09 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen resolved DERBY-2430.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0
       Derby Info: [Release Note Needed]  (was: [Patch Available])

Thanks Narayanan. The patch looks good. Committed revision 517577.
I set the "Release Note Needed" flag to indicate that this change should be mentioned in the
release notes for 10.3. It would be OK to incorporate the release note for this issue into
the release note for DERBY-1610.

>  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
>         Assigned To: V.Narayanan
>             Fix For: 10.3.0.0
>
>         Attachments: setObjectForClobBlob_v1.diff, setObjectForClobBlob_v1.stat
>
>
> 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