db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2702) Modify tests that experience changed behaviour due to enabling Clob Locators
Date Sat, 26 May 2007 17:23:16 GMT

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

V.Narayanan updated DERBY-2702:
-------------------------------

    Attachment: ClobLocatorWorkTestModifications.stat
                ClobLocatorWorkTestModifications.diff

The changes done here are very similar to the test changes done as part
of Derby-2496 to enable Blob locator support. The only difference being
the Clob related tests are addressed here.

M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/ClobTest.java

- Adjusted tests to not expect Clob objects to be valid after
  transaction commit. 

M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/PreparedStatementTest.java

- Adjusted tests to not expect Clob objects to be valid after
  transaction commit.
- Rewrote testSetClobLengthless to take advantage of the existence of
  Connection.createClob 

M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/ResultSetTest.java

- Adjusted tests to not expect Clob objects to be valid after
  transaction commit. 

M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/BlobClob4BlobTest.java

- testClobAfterCommit is changed to test that Blobs on the client is no longer valid after

  transaction has committed.

- testClobAfterClosingConnection has been changed to not expect a Clob to be valid in the
  client after connection has been closed.

- testSelfDestructiveClob2 has been changed to expect an IOException from the Clob
  after the table associated with the Clob is deleted. The IOException that is obtained
  contains a null value when getCause() is used. There seems to be an issue with the
  exception not being changed inside this IOException. The test has been changed to verify
  that an exception is thrown in the NetworkClient case.

M      java/client/org/apache/derby/client/net/NetStatementRequest.java

- Enabled the LID constants that would make the NetworkClient request the NetworkServer request

  for locators.

I have done one integrated run of all the patches attached to issues indicated here as dependencies
and the test fixes here are directly related to the failures that I encountered. 

I am running junit All again after fixing these failures.

I am running junit all with all the dependent patches and shall revert back with the results.

Pls consider this patch for reviews and comments.

> Modify tests that experience changed behaviour due to enabling Clob Locators
> ----------------------------------------------------------------------------
>
>                 Key: DERBY-2702
>                 URL: https://issues.apache.org/jira/browse/DERBY-2702
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: V.Narayanan
>         Assigned To: V.Narayanan
>         Attachments: ClobLocatorWorkTestModifications.diff, ClobLocatorWorkTestModifications.stat
>
>


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