db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tiago R. Espinha (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-3839) Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorJDBC30.sql" to junit.
Date Fri, 01 May 2009 22:13:30 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705146#action_12705146
] 

Tiago R. Espinha edited comment on DERBY-3839 at 5/1/09 3:11 PM:
-----------------------------------------------------------------

This is a working patch of this test. I haven't yet ran suites.All nor derbyall but will do
so if this patch is considered for committal.

Keep in mind that this test has two workarounds:
- It drops the 'FOR UPDATE' clause of some of the fixtures as they were causing crashes (on
both embedded and client/server)

- It has two separate behaviours (for embedded and client/server) on the tests testPositionPurgedRow
and testPositionPurgedPage.

Also, my last comment was wrong. It is the client driver's results that aren't faithful to
those of the original test. As can be seen on the repro class I have attached, the underlying
changes to a table aren't replicated to an already open cursor of that table. Is this by design?
Considering it only happens on the client driver?

      was (Author: espinha):
    This is a working patch of this test. I haven't yet ran suites.All nor derbyall but will
do so if this patch is considered for committal.

Keep in mind that this test has two workarounds:
- It drops the 'FOR UPDATE' clause of some of the fixtures as they were causing crashes (on
both embedded and client/server)

- It has to separate behaviours (for embedded and client/server) on the tests testPositionPurgedRow
and testPositionPurgedPage.

Also, my last comment was wrong. It is the client driver's results that aren't faithful to
those of the original test. As can be seen on the repro class I have attached, the underlying
changes to a table aren't replicated to an already open cursor of that table. Is this by design?
Considering it only happens on the client driver?
  
> Convert "org.apache.derbyTesting.functionTests.tests.store.holdCursorJDBC30.sql" to junit.

> -------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3839
>                 URL: https://issues.apache.org/jira/browse/DERBY-3839
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Junjie Peng
>            Assignee: Tiago R. Espinha
>         Attachments: derby-3839-1.patch, derby-3839-1.stat, derby-3839.patch, derby-3839.patch,
ReproHoldCursorBug.java, ReproHoldCursorBug.java, ReproHoldCursorBug.java
>
>


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