[
https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2770:
--------------------------------------
Derby Info: [Regression] (was: [Regression, Patch Available])
Committed derby-2770-2b.diff with revision 545910.
I noticed that there are many comments in BlobClob4BlobTest that say
//The same SQLState String BLOB_ACCESSED_AFTER_COMMIT
//is used for LOB's(Both Clob and Blob). Ensure that
//we get the expected exception by comparing the SQLState.
These comments should be updated to reflect the changed SQL state.
The new error message uses the term "the Blob/Clob's transaction". Would it be
clearer to say "the transaction in which the Blob/Clob was created"?
> 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: Øystein Grøvlen
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2770-1a.diff, derby-2770-2a.diff,
> derby-2770-2a.stat, derby-2770-2b.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.
