db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2587) Connection.createClob() and Connection.createBlob() need to return locator support enabled LOB objects in the NetworkClient
Date Wed, 02 May 2007 21:14:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493212
] 

Rick Hillegas commented on DERBY-2587:
--------------------------------------

Thanks for the changes, Narayanan. We're almost there. I think that the SQLState comparisons
need to use ExceptionUtil.getSQLStateFromIdentifier() in order to guarantee that you only
use the leading 5 characters of the message ID. I realize that this looks moot in this case
since this message ID is only 5 characters long to begin with. But, in the future, someone
may decorate that message ID with trailing information--and that will break the comparison
in CallableLocatorProcedures.

> Connection.createClob() and Connection.createBlob() need to return locator support enabled
LOB objects in the NetworkClient
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2587
>                 URL: https://issues.apache.org/jira/browse/DERBY-2587
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: V.Narayanan
>         Assigned To: V.Narayanan
>         Attachments: ConnectionLocatorWork_v1.diff, ConnectionLocatorWork_v1.stat, ConnectionLocatorWork_v2.diff,
ConnectionLocatorWork_v2.stat
>
>


-- 
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