[ http://issues.apache.org/jira/browse/DERBY-1045?page=comments#action_12367840 ]
Bryan Pendleton commented on DERBY-1045:
----------------------------------------
Are we talking about the diff in lang/forupdate.sql which reads:
59 del
< ERROR (no SQLState): Invalid cursor name "C1" in the Update/Delete statement.
59a59
> ERROR 42X30: Cursor 'SQL_CURLH000C1' not found. Verify that autocommit is OFF.
If so, then this problem did reproduce for me.
The problem, I believe, is a combination of DERBY-213 and DERBY-821, which both involve the
handling of forward-only result sets where all the rows have been exhausted.
The test does:
-- . implicit update test for updatable spec
-- this will end up being read only; we know because the delete is refused
get cursor c1 as 'select i, v from t1 where i is not null';
next c1;
-- the delete will get a 'cursor not updatable' execution error, but won't get
-- a compile time error
delete from t1 where current of c1;
close c1;
DERBY-213 (http://svn.apache.org/viewcvs?rev=264128&view=rev) changed the handling of
the delete statement as follows:
delete from t1 where current of c1;
-ERROR (no SQLState): Invalid cursor name "C1" in the Update/Delete statement.
+ERROR 42X23: Cursor SQL_CURLH000C1 is not updatable.
DERBY-821 (http://svn.apache.org/viewcvs?rev=377367&view=rev) changed the handling of
the delete statement as follows:
delete from t1 where current of c1;
-ERROR 42X23: Cursor SQL_CURLH000C1 is not updatable.
+ERROR 42X30: Cursor 'SQL_CURLH000C1' not found. Verify that autocommit is OFF.
It seems that the point of the test is to verify that an UPDATE on a read-only cursor is refused
with a "not-updateable" error,
in which case perhaps the test needs to be enhanced, to ensure that the DERBY-821 changes
don't automatically close
the table before the delete statement is issued?
> forupdate.sql , holdCursorIJ.sql ..etc are failing when run with 10.1 client againest
trunk
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-1045
> URL: http://issues.apache.org/jira/browse/DERBY-1045
> Project: Derby
> Type: Bug
> Versions: 10.2.0.0
> Environment: Java Version: 1.5.0_02
> Java Vendor: Sun Microsystems Inc.
> Java home: d:\dev\src\jdk15\jre
> Java classpath: d:/dev/src/classes/derby.jar;d:/dev/src/classes/derbytools.jar;d:/dev/src/classes/derbynet.jar;d:/dev/src/classes/v10_1_client/derbyclient.jar;d:/dev/src/classes/functionTests.jar;d:/dev/src/classes/v10_1_client/derbyTesting.jar;d:/dev/src/tools/java/jndi/fscontext.jar;d:/dev/src/tools/java/junit.jar;d:/dev/src/classes/derbyLocale_zh_TW.jar;d:/dev/src/classes/derbyLocale_zh_CN.jar;d:/dev/src/classes/derbyLocale_pt_BR.jar;d:/dev/src/classes/derbyLocale_ko_KR.jar;d:/dev/src/classes/derbyLocale_ja_JP.jar;d:/dev/src/classes/derbyLocale_it.jar;d:/dev/src/classes/derbyLocale_fr.jar;d:/dev/src/classes/derbyLocale_es.jar;d:/dev/src/classes/derbyLocale_de_DE.jar;
> OS name: Windows 2000
> OS architecture: x86
> OS version: 5.0
> Java user dir: D:\dev\src\JarResults.2006-02-22\jdk15_derbynetclientmats_client_v101
> java.specification.name: Java Platform API Specification
> java.specification.version: 1.5
> --------- Derby Information --------
> JRE - JDBC: J2SE 5.0 - JDBC 3.0
> [D:\dev\src\classes\derby.jar] 10.2.0.0 alpha - (380027)
> [D:\dev\src\classes\derbytools.jar] 10.2.0.0 alpha - (380027)
> [D:\dev\src\classes\derbynet.jar] 10.2.0.0 alpha - (380027)
> [D:\dev\src\classes\v10_1_client\derbyclient.jar] 10.1.2.3 - (379660)
> Reporter: Suresh Thalamati
> Attachments: derbynetclientmats_report.txt
>
> derbynetclientmats/derbynetmats/derbynetmats.fail:lang/forupdate.sql
> derbynetclientmats/derbynetmats/derbynetmats.fail:lang/holdCursorIJ.sql
> derbynetclientmats/derbynetmats/derbynetmats.fail:store/holdCursorJDBC30.sql
> derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/LOBTest.java
> derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/blobclob4BLOB.java
> derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/parameterMapping.java
> derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/setTransactionIsolation.java
> derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/metadataJdbc20.java
> derbynetclientmats/derbynetmats/derbynetmats.fail:jdbcapi/connectionJdbc20.java
> Sample diff :
> *** Start: forupdate jdk1.5.0_02 DerbyNetClient derbynetmats:derbynetmats 2006-02-23
07:30:19 ***
> 23 del
> < ERROR 42X01: Syntax error: Encountered "<EOF>" at line 1, column 23.
> 23a23
> > ERROR 42X01: Syntax error: Encountered "<EOF>" at line 3, column 23.
> 59 del
> < ERROR (no SQLState): Invalid cursor name "C1" in the Update/Delete statement.
> 59a59
> > ERROR 42X30: Cursor 'SQL_CURLH000C1' not found. Verify that autocommit is OFF.
> 132 del
> < ERROR (no SQLState): Invalid cursor name "C4" in the Update/Delete statement.
> 132a132
> > ERROR 42X30: Cursor 'SQL_CURLH000C1' not found. Verify that autocommit is OFF.
> 135 del
> < ERROR (no SQLState): Invalid cursor name "C4" in the Update/Delete statement.
> 135a135
> > ERROR 42X30: Cursor 'SQL_CURLH000C1' not found. Verify that autocommit is OFF.
> 180 del
> < ERROR 42X01: Syntax error: Encountered "." at line 1, column 34.
> 180a180
> > ERROR 42X01: Syntax error: Encountered "." at line 3, column 34.
> Test Failed.
> *** End: forupdate jdk1.5.0_02 DerbyNetClient derbynetmats:derbynetmats 2006
--
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
|