[
https://issues.apache.org/jira/browse/DERBY-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502326
]
Kristian Waagan commented on DERBY-2771:
----------------------------------------
Øystein,
Actually, I logged this Jira as part of work on DERBY-2770. Now it turns out
that I fixed that in an incorrect way.
XJ217 was not thrown as the top-level exception, but was at the bottom of the
exception chain. I think it is okay to chain the XJ217.
So that leaves us with two different states (XJ215 and XJ073) for embedded and
client, which is another issue.
Feel free to close this issue as invalid.
> Unhelpful error message provided when accesing Blob after commit in the
> client driver
> -------------------------------------------------------------------------------------
>
> Key: DERBY-2771
> URL: https://issues.apache.org/jira/browse/DERBY-2771
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.3.0.0
> Reporter: Kristian Waagan
> Priority: Minor
>
> When accessing a Blob after commit in the embedded driver you get one of
> these messages:
> XJ215.S=You cannot invoke other java.sql.Clob/java.sql.Blob methods after
> calling the free() method.
> XJ073.S=The data in this BLOB or CLOB is no longer available. The
> BLOB/CLOB''s transaction may be committed, or its connection is closed.
> With the client driver you get this:
> XJ217.S=The locator that was supplied for this CLOB/BLOB is invalid
> Is this error message too technical?
> Should the embedded and the client driver behave in a consistent manner?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
