[
https://issues.apache.org/jira/browse/DERBY-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683631#action_12683631
]
Kathey Marsden commented on DERBY-3656:
---------------------------------------
Tiago asked:
>Is it really needed to run the tests for this type of patch though? It's a
>through and through string change.
Many of the tests are still canon based and may have the text of the message in
the output and need updating.
Also changing an xml file, it's easy to miss a bracket and break the whole
thing, so always safest to clobber, build and run tests. You'll sleep better
at night, knowing you'll get a clean commit. Kick them off before you leave for
the day and it's no extra trouble.
> ERROR XJ073: The data in this BLOB or CLOB is no longer available. should
> include the possibility that the lob has been freed
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3656
> URL: https://issues.apache.org/jira/browse/DERBY-3656
> Project: Derby
> Issue Type: Improvement
> Components: JDBC, Newcomer
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Tiago R. Espinha
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: patch3656.patch
>
>
> The message XJ073 says:
> ERROR XJ073: The data in this BLOB or CLOB is no longer available. The
> BLOB/CLOB's transaction may be committed, or its connection is closed.
> but the lob might also not be available because it has been freed. It would
> be good to include that possibility in the error message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
