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] Commented: (DERBY-2702) Modify tests that experience changed behaviour due to enabling Clob Locators
Date Sat, 26 May 2007 17:04:18 GMT

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

V.Narayanan commented on DERBY-2702:

My apologies for the ambiguity in the comment. Locators in an internal concept.

An application cannot request for its usage. The NetworkClient will request the NetworkServer
to send it a locator
instead of the LOB value. 

Enabling was enabling locator support between the Network Client and the NetworkServer

What I meant by this comment was internally locator support has been disabled in the following
places and they should
be enabled.

1) createClob() - Does not return a locator enabled Clob as of now. Please note the
                              disabling done at line no 2216 of am/Connection.java for Blob
                              and a similar disabling done in the patch attached that implements
                               createClob() in the patch attached to issue 2587

2)  NetResultSetRequest - line no 275. This the place where we (The Network Client) request
                                                 locators (To the Network Server) if the ResultSet
contains a LOB

3)  NetStatementRequest - line no 641 where the LID constants are initialized in the SQLDTA
                                                 is sent.

> Modify tests that experience changed behaviour due to enabling Clob Locators
> ----------------------------------------------------------------------------
>                 Key: DERBY-2702
>                 URL: https://issues.apache.org/jira/browse/DERBY-2702
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: V.Narayanan
>         Assigned To: V.Narayanan

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

View raw message