[
https://issues.apache.org/jira/browse/DERBY-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838345#action_12838345
]
Kristian Waagan commented on DERBY-3650:
----------------------------------------
Mike wrote:
-----
I think this would build fine on top of the clone changes that Kristian is
working on in DERBY-4520.
-----
You're probably right, but I think it's time to start ripping something out
soon :)
At least for my own work I feel very much that I have been building my way
around various obstacles. This has caused the complexity to increase, and I
hope that by taking a step back much of it can be reduced.
The good thing is that most of the added complexity has been added for BLOB and
CLOB. That said, I'm not happy about the state of SQLChar. Maybe it is just
because I associate it too much with the SQL data type CHAR, but in theory the
code dealing with CHAR (and VARCHAR) should be a lot simpler than the code
dealing with CLOB.
> 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
> Environment: Mac OSX 10.4
> JDK 1.5.0_13
> Hibernate EntityManager 3.2.1
> Reporter: Golgoth 14
> Attachments: cloning-methods.html, derby-3650-preliminary_2_diff.txt,
> derby-3650-preliminary_2_reworked.diff, derby-3650-preliminary_diff.txt,
> derby-3650_tests_diff.txt, Derby3650EmbeddedRepro.java,
> Derby3650FullClientRepro.java, Derby3650FullRepro.java, Derby3650Repro.java,
> DerbyHibernateTest.zip, testdb.zip, traces_on_FormatIdStream_alloc.txt,
> UnionAll.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
