db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-2770) testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'
Date Thu, 07 Jun 2007 15:30:25 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Øystein Grøvlen updated DERBY-2770:
-----------------------------------

    Attachment: derby-2770-2b.diff

Attached file, derby-2770-2b.diff, changes the client to used the same
SQL state as embedded for Blobs accessed after transaction has
committed.  Since Clob has yet to get the new behavior, there will now
be a difference between client and embedded for Clobs.  However, I
expect that to be fixed by Anurag when it posts his corresponding
patch for Blob.

The following files are changed by this patch:
M      java/engine/org/apache/derby/loc/messages.xml
   Changed error message to reflect that XJ215 is used both after
   free() has been called on a Lob and after the lob's transaction has
   been committed.

M      java/client/org/apache/derby/client/am/CallableLocatorProcedures.java
   Change SQL state to use when locators are invalid from XJ073 to
   XJ215.  Also, Knut Anders has since this method was created, made
   nested exceptions with SQL state available on the client.  Hence,
   we can now check for SQL state directly instead resorting to text
   search of error messages.

M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/BlobClob4BlobTest.java
   Change tests to except the changed SQL state for access after
   commit.


> 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, 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.


Mime
View raw message