You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2008/05/05 17:03:55 UTC

[jira] Updated: (DERBY-1323) Detectability methods rowUpdated, rowInserted, rowDeleted can be called from illegal states in both clients

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

Dag H. Wanvik updated DERBY-1323:
---------------------------------

    Derby Info: [Existing Application Impact, Release Note Needed]  (was: [Patch Available, Release Note Needed, Existing Application Impact])

> Detectability methods rowUpdated, rowInserted, rowDeleted can be called from illegal states in both clients
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1323
>                 URL: https://issues.apache.org/jira/browse/DERBY-1323
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.2.1.6
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>            Priority: Minor
>             Fix For: 10.2.1.6
>
>         Attachments: DERBY-1323-1.diff, DERBY-1323-1.stat, DERBY-1323-2.diff, DERBY-1323-2.stat, Main.java
>
>
> Please see enclosed repro.
> These detectability methods fail to check that they can be called in
> some states. In the repro, calls are allowed while on insert row and
> when after last row. These should both fail. Both clients have the
> same problem. All three detectability methods have the same problem.
> (repro only shows it for a subset of the cases).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.