[
https://issues.apache.org/jira/browse/DERBY-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4278:
-----------------------------------
Urgency: Urgent
I'm marking this issue as Urgent as it seems to be triggered with default
configuration using Derby with Hibernate (and Clobs in the table of course). It
is also a regression, introduced through the new Clob header format code.
Finally, the bug was reported by a user.
> Batch inserts with Clobs fails with the embedded driver
> -------------------------------------------------------
>
> Key: DERBY-4278
> URL: https://issues.apache.org/jira/browse/DERBY-4278
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.5.1.1, 10.6.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: derby-4278-1a-regression_test.diff,
> derby-4278-2a-fix.diff
>
>
> Batch inserts with Clobs fail because Derby is unable to determine if it
> should write the Clob stream header formats using the old 10.4 style format
> or the new 10.5 format.
> More specifically, the access mode (soft upgrade or not) hasn't been set
> specifically by Derby before the stream header has to be generated, and there
> isn't enough context to determine the mode at generation time.
> Bug was reported on derby-user:
> http://www.nabble.com/Hibernate-%2B-Derby---Unable-to-determine-stream-header-for-hibernate-type-%27text%27-td24099674.html
> The bug was reported for Derby used with Hibernate. Possible workarounds are
> to use the client driver or to avoid using batched inserts with Clobs (i.e.
> don't use batched inserts, which may degrade performance, or use a different
> data type).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
