[
https://issues.apache.org/jira/browse/DERBY-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4245:
-----------------------------------
Issue & fix info: [Repro attached] (was: [Repro attached, Patch Available])
Committed patch 3a to trunk with revision 791398.
Is it worth making LimitInputStream.mark(int) do nothing and have reset() throw
an exception to be on the safe side?
With the possible exception of mark/reset above, I don't expect to do any more
work on this issue before I port the fixes to the 10.5 branch.
> Sorting a table containing a CLOB fails after upgrade to 10.5
> -------------------------------------------------------------
>
> Key: DERBY-4245
> URL: https://issues.apache.org/jira/browse/DERBY-4245
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.5.1.1
> Reporter: Knut Anders Hatlen
> Assignee: Kristian Waagan
> Fix For: 10.5.1.2, 10.6.0.0
>
> Attachments: derby-4245-0a-preview.diff, derby-4245-1a-test.diff,
> derby-4245-1b-test.diff, derby-4245-1c-test.diff,
> derby-4245-2a-sqlclob_fix.diff, derby-4245-3a-unread_bytes_fix.diff,
> derby-4245-4a-adjust_sort_buffer_test.diff, MixedVersionClob.java
>
>
> When sorting a table containing a CLOB column in a database that has been
> soft-upgraded from 10.4.2.0 to 10.5.1.1, the query fails with a
> NullPointerException.
> Reported on derby-user:
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200905.mbox/%[email protected]%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
