[
https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502278
]
Knut Anders Hatlen commented on DERBY-2770:
-------------------------------------------
Just guessing here, but I noticed this:
- both BLOBCREATELOCATOR and CLOBCREATELOCATOR call addLOBMapping
- EmbedBlob's constructors call addLOBMapping, but EmbedClob's constructors
don't
- Narayanan's test uses createBlob()/createClob(), hence addLOBMapping is
always called
- testBlobAfterCommit() and testClobAfterCommit() get the lobs from
ResultSet.get[BC]lob(), hence addLOBMapping is only called for the BLOB test
> testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL
> state. expected:<XJ[073]> but was:<XJ[215]>'
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2770
> URL: https://issues.apache.org/jira/browse/DERBY-2770
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0
> Environment: OS: Solaris 10 6/06 s10x_u2wos_09a X86 64bits - SunOS
> 5.10 Generic_118855-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
> Reporter: Ole Solberg
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, ExceptionTest.java
>
>
> testBlobAfterCommit(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)junit.framework.ComparisonFailure:
> Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>
> after
> r544777 / DERBY-2729
> See
> http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/544778-org.apache.derbyTesting.functionTests.suites.All_diff.txt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
