[
https://issues.apache.org/jira/browse/DERBY-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489934
]
V.Narayanan commented on DERBY-2565:
------------------------------------
During the implementation of Stored procedures related to Locators these
methods had dummy implementations because all calls inside BrokeredConnection
are forwarded to the underlying physical connection. So the assumption was that
the implementations in BrokeredConnection would never be called directly.
When we however are working with XA transactions we would get a
BrokeredConnection object.
As can be seen in the patch attached to DRDA work related to PreparedStatement
and CallableStatement http://issues.apache.org/jira/browse/DERBY-2506 we would
do a
//Map the locator value to the Blob object in the
//Hash map.
java.sql.Blob blobFromLocator = (java.sql.Blob)
database.getConnection().getLOBMapping(paramVal);
to map the locator value to the Blob object in the HashMap. When working with
XA transactions database.getConnection() would return a BrokeredConnection
object and this call would fail.
Hence the implementations of the locator related methods also need to be
forwarded to the underlying physical connection.
> BrokeredConnection needs to forward implementations of locator related
> methods in EngineConnection to the underlying physical connection
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2565
> URL: https://issues.apache.org/jira/browse/DERBY-2565
> 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.
