[
https://issues.apache.org/jira/browse/DERBY-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Øystein Grøvlen updated DERBY-2519:
-----------------------------------
Attachment: derby-2519.diff
Attached patch, derby-2519.diff, contains the fixes described above. All
changes are in a single file:
NOTE: It turned out that in order for the test to use ResultSet.updateClob,
Clob.setString is needed. This is not yet implemented in the embedded driver,
but there is a patch for this (DERBY-2346) which is under review. I will mark
this issue as blocked by that DERBY-2346, and not set the patch available flag
until DERBY-2346 has been committed.
> Clean-up in BlobClob4BlobTest
> -----------------------------
>
> Key: DERBY-2519
> URL: https://issues.apache.org/jira/browse/DERBY-2519
> Project: Derby
> Issue Type: Test
> Components: Test
> Environment: Any
> Reporter: Øystein Grøvlen
> Assigned To: Øystein Grøvlen
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-2519.diff
>
>
> Will attach patch to this issue that does the following clean-up in
> the test:
> * Do a transaction rollback in tearDown() before dropping tables.
> This prevents failures when dropping tables due to open result
> sets.
> * Commit work in setUp(). Otherwise, the change above may roll
> back the created tables on failure and tearDown() will attempt
> drop non-existing tables.
> * Test contains a set of test cases called xTest... that seems to
> originally have been called so because they were excluded from
> running in client/server mode. They are now run in both embedded
> and client/server so they should be renamed so they are
> automatically made part of the suite.
> * ResultSet.update[BC]lob has now been implemented and should be
> used in the above mentioned test cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
