You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Øystein Grøvlen (JIRA)" <ji...@apache.org> on 2007/06/07 09:52:25 UTC
[jira] Commented: (DERBY-2771) Unhelpful error message provided
when accesing Blob after commit in the client driver
[ https://issues.apache.org/jira/browse/DERBY-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502256 ]
Øystein Grøvlen commented on DERBY-2771:
----------------------------------------
The client has code for translating XJ217 into something else. It seemed to work earlier, but now it seems to be broken. I am looking into it.
> 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.