[
https://issues.apache.org/jira/browse/DERBY-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478448
]
Knut Anders Hatlen commented on DERBY-2257:
-------------------------------------------
> All Brokered calls are forwarded to the rootConnection. Hence it wasn't
> necessary to have an implementation for these methods here
Perhaps a comment in the code explaining this would be helpful?
> The test cases that test for failure are in the ClobStoredProcedureTest
> class. All of them can be explained by considering the following example.
> [...]
This problem sounds related to the problems described in DERBY-1629 and
DERBY-1440. I think the exceptions thrown in stored procedures are supposed to
be wrapped in an SQLException with a specific SQL state, but I don't know the
details.
> Also the code in which I check for the SQLException is temporary and will be
> removed once the Clob locator methods are added.
The tests for BLOBRELEASELOCATOR and CLOBRELEASELOCATOR also ignore expected
SQLExceptions without checking SQL state. That code is not temporary, is it?
> Implementing the stored procedures called by the LOB related JDBC methods
> -------------------------------------------------------------------------
>
> Key: DERBY-2257
> URL: https://issues.apache.org/jira/browse/DERBY-2257
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC
> Environment: All environments
> Reporter: V.Narayanan
> Assigned To: V.Narayanan
> Attachments: Expln_StoredProc_LOB.txt, Expln_StoredProc_LOB_v2.txt,
> StoredProcedure_v3.diff, StoredProcedure_v3.stat, StoredProcedure_v4.diff,
> StoredProcedure_v4.stat, StoredProcedure_v5.diff, StoredProcedure_v5.stat,
> StoredProcedure_v6.diff, StoredProcedure_v6.stat, StoredProcedure_v7.diff,
> StoredProcedure_v7.stat, StoredProcedures_v1.diff, StoredProcedures_v1.stat,
> StoredProcedures_v2.diff, StoredProcedures_v2.stat
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
