[
https://issues.apache.org/jira/browse/DERBY-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595004#action_12595004
]
Mamta A. Satoor commented on DERBY-3650:
----------------------------------------
I spent some time on this jira entry. In the test cases attached by Kathey,
Derby3650FullRepro.java and UnionAll.java, there are 2 tables TAB and TAB2.
There is one row in table TAB which has the CLOB column and 2 rows in table
TAB2. It appears that for loj case, we are looking at TAB only once to get the
CLOB and using that same row from TAB twice for the 2 rows returned from TAB2
but in case of union, it looks like we get the row from TAB twice once for each
row in TAB2. I am not sure why there is a difference in how and when the row is
fetched from TAB but may be explore that difference further more. May be in loj
case, we should not free the CLOB so it can be reused. Not exactly sure but I
thought I would share what I found.
> Derby + Hibernate JPA 3.2.1 problem on entity with Blob/Clob
> ------------------------------------------------------------
>
> Key: DERBY-3650
> URL: https://issues.apache.org/jira/browse/DERBY-3650
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.1.3
> Environment: Mac OSX 10.4
> JDK 1.5.0_13
> Hibernate EntityManager 3.2.1
> Reporter: Golgoth 14
> Attachments: Derby3650EmbeddedRepro.java, Derby3650FullRepro.java,
> Derby3650Repro.java, DerbyHibernateTest.zip, testdb.zip,
> traces_on_FormatIdStream_alloc.txt, UnionAll.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
