CLOB values incorrectly stored on disk using the old header format
------------------------------------------------------------------
Key: DERBY-4543
URL: https://issues.apache.org/jira/browse/DERBY-4543
Project: Derby
Issue Type: Bug
Components: JDBC, Store
Affects Versions: 10.6.0.0
Reporter: Kristian Waagan
Assignee: Kristian Waagan
Fix For: 10.6.0.0
The logic determining whether CLOB values should be stored using the old (pre
10.5) or the new header format has two bugs, which sometimes causes the old
format to be used even though the new one should be used.
The naming of the relevant methods are also problematic, as we're not really
interested in whether we are in soft-upgrade mode or not. If you soft-upgrade
from 10.5 to 10.6, the new header format should still be used.
The consequences of these bugs are potential loss of performance for certain
operations on CLOB values and in some cases it might cause a crash if the
source stream cannot be rewinded/reset.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
