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)" <de...@db.apache.org> on 2006/05/19 03:38:07 UTC

[jira] Closed: (DERBY-1266) Client: Attempted deleteRow or updateRow while on insert row gives wrong error message

     [ http://issues.apache.org/jira/browse/DERBY-1266?page=all ]
     
Dag H. Wanvik closed DERBY-1266:
--------------------------------


Fixed.

> Client: Attempted deleteRow or updateRow while on insert row gives wrong error message
> --------------------------------------------------------------------------------------
>
>          Key: DERBY-1266
>          URL: http://issues.apache.org/jira/browse/DERBY-1266
>      Project: Derby
>         Type: Bug

>   Components: Network Client
>     Versions: 10.2.0.0
>  Environment: any
>     Reporter: Dag H. Wanvik
>     Assignee: David Van Couvering
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: DERBY-1266-1.diff, DERBY-1266-2.diff
>
> This fragment from deleteRowX shows the problem:
> > if (isOnInsertRow_) {
> >       throw new SqlException(agent_.logWriter_, 
> >           new MessageId(SQLState.CURSOR_NOT_POSITIONED_ON_INSERT_ROW));
> > }
> It should be the opposite: the problem is that the cursor *is* on the
> insert row, not that it isn't.
> These is a similar error in updateRowX.
> The client master files for updatableResultSet show the problem, so
> the masters are wrong, too.
> > Negative Test 39.a - run updateRow on insertRow
> > SQL State: XJ086
> > Got expected exception: This method cannot be invoked while the
>   cursor is not on the insert row or if the concurrency of this 
>   ResultSet object is CONCUR_READ_ONLY. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira