[
https://issues.apache.org/jira/browse/DERBY-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512392
]
Knut Anders Hatlen commented on DERBY-2923:
-------------------------------------------
The fix looks fine to me too. I'm running the regression tests on 10.3 now and
will commit when they have completed.
I noticed one potential improvement for later: After this change, we always
convert the indexes we put into rsExtPositions from 1 based to 0 based, and
always convert them back to 1 based when we retrieve the values. It would be
good if we skipped the 1->0 conversion in addExtDtaObject() and the 0->1
conversion in isExtDtaValueNullable() and just stored the indexes 1 based in
rsExtPositions.
> Incorrect reading of nullable Blob/Clob columns during soft upgrade with
> client/server
> --------------------------------------------------------------------------------------
>
> Key: DERBY-2923
> URL: https://issues.apache.org/jira/browse/DERBY-2923
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.3.0.0, 10.3.1.0, 10.3.1.1
> Environment: Client/server soft upgrade
> Reporter: Øystein Grøvlen
> Assignee: Øystein Grøvlen
> Priority: Blocker
> Fix For: 10.3.1.2
>
> Attachments: SimpleBlobTest.java, softupgradefix.diff
>
>
> Select operations with client/server and soft upgrade mode will not see first
> byte of the Blob/Clob if the LOB column is nullable.
> The reason seems to be that during soft upgrade, the network server does not
> prepend the LOB data with the byte indicating whether the column is null or
> not. Hence, the first data byte will be interpreted by the client as the
> null byte, and the reading of the LOB will start at the second byte.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
