[
https://issues.apache.org/jira/browse/DERBY-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden resolved DERBY-3650.
-----------------------------------
Resolution: Fixed
reclosing. This will come off the backport list. Comments say:
Note that this fix won't be back-ported, because the underlying clone
functionality is hard to back-port (major changes).
I added the derby_backport_reject_10_5 label.
> internal multiple references from different rows to a single BLOB/CLOB stream
> leads to various errors when second reference used.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3650
> URL: https://issues.apache.org/jira/browse/DERBY-3650
> Project: Derby
> Issue Type: Bug
> Components: Network Client, SQL, Store
> Affects Versions: 10.3.3.0, 10.4.1.3, 10.5.3.0, 10.6.1.0
> Environment: Mac OSX 10.4
> JDK 1.5.0_13
> Hibernate EntityManager 3.2.1
> Reporter: Golgoth 14
> Assignee: Kristian Waagan
> Labels: derby_backport_reject_10_5
> Fix For: 10.6.1.0
>
> Attachments: Derby3650EmbeddedRepro.java,
> Derby3650FullClientRepro.java, Derby3650FullRepro.java, Derby3650Repro.java,
> DerbyHibernateTest.zip, UnionAll.java, cloning-methods.html,
> derby-3650-preliminary_2_diff.txt, derby-3650-preliminary_2_reworked-1b.diff,
> derby-3650-preliminary_2_reworked.diff, derby-3650-preliminary_diff.txt,
> derby-3650_tests_diff.txt, testdb.zip, traces_on_FormatIdStream_alloc.txt
>
>
> Derby + Hibernate JPA 3.2.1 problem on entity with Blob/Clob
> Hi,
> I'm using Derby in Client - Server mode with Hibernate JPA EJB 3.0.
> When a query on an entity containing a Clob and some joins on other entites
> is executed, an exception with the following message is thrown:
> 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.
> This problem occurs when the property "hibernate.max_fetch_depth" is greater
> than 0.
> When hibernate.max_fetch_depth=0, the query works.
> If Derby is configured in embedded mode, the query works independently of the
> value of hibernate.max_fetch_depth.
> On the Hibernate's documentation, the advised value of
> hibernate.max_fetch_depth is 3.
> Could you explain me if I made something wrong ?
> Thank you.
> Stephane
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
