[jira] Resolved: (DERBY-501) Client and embedded drivers differ on invoking a procedure that returns a single Dynamic resultSet using CallableStatement.executeQuery()

[ http://issues.apache.org/jira/browse/DERBY-501?page=all ] Knut Anders Hatlen resolved DERBY-501: -- Fix Version: 10.2.0.0 Resolution: Fixed Committed revision 414795. Client and embedded drivers differ on invoking a procedure that

[jira] Commented: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=comments#action_12416518 ] Knut Anders Hatlen commented on DERBY-137: -- I have (or more precisely, a test program of mine has) gone through all the DatabaseMetaData methods and compared them to

[jira] Commented: (DERBY-1279) Bad column name in DatabaseMetaData.getColumns()

[ http://issues.apache.org/jira/browse/DERBY-1279?page=comments#action_12416715 ] Knut Anders Hatlen commented on DERBY-1279: --- As far as I can see, getColums() doesn't return any column named SCOPE_CATLOG or SCOPE_CATALOG (but it should return

[jira] Commented: (DERBY-1183) Client java.sql.ResultSet.getCursorName() does not return the correct cursor name for Statements after the first execution

[ http://issues.apache.org/jira/browse/DERBY-1183?page=comments#action_12416892 ] Knut Anders Hatlen commented on DERBY-1183: --- Dag, I see two failures in derbyall with this patch. From lang/updatableResultSet.java I got a diff that was thousands

[jira] Created: (DERBY-1433) Client driver does not handle string literals containing where current of correctly

Client driver does not handle string literals containing where current of correctly - Key: DERBY-1433 URL: http://issues.apache.org/jira/browse/DERBY-1433 Project: Derby Type: Bug

[jira] Updated: (DERBY-1433) Client driver does not handle string literals containing where current of correctly

[ http://issues.apache.org/jira/browse/DERBY-1433?page=all ] Knut Anders Hatlen updated DERBY-1433: -- Attachment: cursor.java Attached a repro for the bug (cursor.java). When the program is run, it is supposed to print Writing where current of in

[jira] Updated: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=all ] Knut Anders Hatlen updated DERBY-137: - Attachment: derby-137-v1.diff derby-137-v1.stat The attached patch changes the data types and adds missing columns so that the result

[jira] Updated: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=all ] Knut Anders Hatlen updated DERBY-137: - Derby Info: [Patch Available] Patch is available and ready for review. Thanks! Derby metadata always returns JDBC 2 result sets, even when JDBC 3

[jira] Commented: (DERBY-1314) Differences between client and embedded when invoking stored procedures using Statement.executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1314?page=comments#action_12417104 ] Knut Anders Hatlen commented on DERBY-1314: --- Does anyone have comments to the patch? If not, I plan to commit in a couple of days. Differences between client and

[jira] Assigned: (DERBY-1393) PreparedStatement.setObject(Object,int,int) should throw for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1393?page=all ] Knut Anders Hatlen reassigned DERBY-1393: - Assign To: Knut Anders Hatlen PreparedStatement.setObject(Object,int,int) should throw for unsupported types

[jira] Resolved: (DERBY-1183) Client java.sql.ResultSet.getCursorName() does not return the correct cursor name for Statements after the first execution

[ http://issues.apache.org/jira/browse/DERBY-1183?page=all ] Knut Anders Hatlen resolved DERBY-1183: --- Resolution: Fixed Dag, I made two changes to your last patch before committing. 1) A couple of println statements had been added to

[jira] Resolved: (DERBY-1036) Embedded and client differ with regard to Statement.setCursor Name. client will disallow duplicate cursor names. Embedded will allow it.

[ http://issues.apache.org/jira/browse/DERBY-1036?page=all ] Knut Anders Hatlen resolved DERBY-1036: --- Fix Version: 10.2.0.0 Resolution: Fixed Dag's patch for DERBY-1183 and this issue committed into trunk with revision 416661.

[jira] Closed: (DERBY-1314) Differences between client and embedded when invoking stored procedures using Statement.executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1314?page=all ] Knut Anders Hatlen closed DERBY-1314: - Fix Version: 10.2.0.0 Resolution: Fixed Committed revision 416696. Differences between client and embedded when invoking stored

[jira] Assigned: (DERBY-1364) Client driver does not roll back the effects of a stored procedure when incorrectly invoked by executeQuery()/executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1364?page=all ] Knut Anders Hatlen reassigned DERBY-1364: - Assign To: Knut Anders Hatlen Client driver does not roll back the effects of a stored procedure when incorrectly invoked by

[jira] Commented: (DERBY-1445) Add new streaming overloads and modify some existing ones.

[ http://issues.apache.org/jira/browse/DERBY-1445?page=comments#action_12417495 ] Knut Anders Hatlen commented on DERBY-1445: --- Hi Narayanan, It seems like your editor has eight character tabs, so your indentation doesn't always match the

[jira] Commented: (DERBY-1275) Provide a way to enable client tracing without changing the application

[ http://issues.apache.org/jira/browse/DERBY-1275?page=comments#action_12417497 ] Knut Anders Hatlen commented on DERBY-1275: --- Hi Kathey, I think your approach sounds reasonable. It is definitely good to have some simple way (documented or

[jira] Commented: (DERBY-955) Get derbyall on jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-955?page=comments#action_12417553 ] Knut Anders Hatlen commented on DERBY-955: -- I plan to review and commit Olav's patch. If someone has comments or is planning to review, please let me know. Thanks!

[jira] Updated: (DERBY-1425) testProtocol hangs with 10.1 client talking to 10.2 server

[ http://issues.apache.org/jira/browse/DERBY-1425?page=all ] Knut Anders Hatlen updated DERBY-1425: -- Attachment: ddmreader_initialize.diff ddmreader_initialize.diff contains the changes to DDMReader which made the hang go away. I have not had time

[jira] Commented: (DERBY-955) Get derbyall on jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-955?page=comments#action_12417592 ] Knut Anders Hatlen commented on DERBY-955: -- The patch looks clean and simple. Ran derbyall on jdk15 with one error (runtimeinfo.java which fails more or less all the

[jira] Updated: (DERBY-1364) Client driver does not roll back the effects of a stored procedure when incorrectly invoked by executeQuery()/executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1364?page=all ] Knut Anders Hatlen updated DERBY-1364: -- Attachment: derby-1364-v1.diff derby-1364-v1.stat Attached a patch (derby-1364-v1.diff) which attempts to fix this issue.

[jira] Updated: (DERBY-1364) Client driver does not roll back the effects of a stored procedure when incorrectly invoked by executeQuery()/executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1364?page=all ] Knut Anders Hatlen updated DERBY-1364: -- Derby Info: [Patch Available] Client driver does not roll back the effects of a stored procedure when incorrectly invoked by

[jira] Created: (DERBY-1455) Intermittent failure in derbynet/runtimeinfo.java

Intermittent failure in derbynet/runtimeinfo.java - Key: DERBY-1455 URL: http://issues.apache.org/jira/browse/DERBY-1455 Project: Derby Type: Bug Components: Test Versions: 10.2.0.0 Reporter: Knut

[jira] Updated: (DERBY-1455) Intermittent failure in derbynet/runtimeinfo.java

[ http://issues.apache.org/jira/browse/DERBY-1455?page=all ] Knut Anders Hatlen updated DERBY-1455: -- Attachment: derby-1455.diff derby-1455.stat Attached a patch which seems to fix the problem. I ran the test 421 times with the jar

[jira] Updated: (DERBY-1455) Intermittent failure in derbynet/runtimeinfo.java

[ http://issues.apache.org/jira/browse/DERBY-1455?page=all ] Knut Anders Hatlen updated DERBY-1455: -- Derby Info: [Patch Available] Intermittent failure in derbynet/runtimeinfo.java - Key:

[jira] Commented: (DERBY-1425) testProtocol hangs with 10.1 client talking to 10.2 server

[ http://issues.apache.org/jira/browse/DERBY-1425?page=comments#action_12417731 ] Knut Anders Hatlen commented on DERBY-1425: --- Yes, the test still fails, but I don't think a separate issue is needed since the test should fail in a mixed

[jira] Closed: (DERBY-1455) Intermittent failure in derbynet/runtimeinfo.java

[ http://issues.apache.org/jira/browse/DERBY-1455?page=all ] Knut Anders Hatlen closed DERBY-1455: - Fix Version: 10.2.0.0 Resolution: Fixed Committed revision 417131. Intermittent failure in derbynet/runtimeinfo.java

[jira] Commented: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=comments#action_12417738 ] Knut Anders Hatlen commented on DERBY-137: -- I plan to commit this patch tomorrow. If someone is planning to review, please let me know and I'll hold the commit.

[jira] Commented: (DERBY-1393) PreparedStatement.setObject(Object,int,int) should throw for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1393?page=comments#action_12417760 ] Knut Anders Hatlen commented on DERBY-1393: --- Does Derby support JAVA_OBJECT? Types.JAVA_OBJECT is used in the code, but I have not been able to find out how an

[jira] Commented: (DERBY-1450) jdbcapi/parameterMetaDataJdbc30.java fails with 10.1 client and 10.2 server

[ http://issues.apache.org/jira/browse/DERBY-1450?page=comments#action_12417800 ] Knut Anders Hatlen commented on DERBY-1450: --- This is caused by a test case for DERBY-44 which is supposed to test a) that Derby understands the LIKE/ESCAPE syntax

[jira] Updated: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=all ] Knut Anders Hatlen updated DERBY-137: - Attachment: derby-137-v2.diff derby-137-v2.stat Thank you very much for reviewing, A B! You are right; NULLABLE, SEARCHABLE,

[jira] Commented: (DERBY-1445) Add new streaming overloads and modify some existing ones.

[ http://issues.apache.org/jira/browse/DERBY-1445?page=comments#action_12418015 ] Knut Anders Hatlen commented on DERBY-1445: --- Thanks Narayanan and Kristian! I will look into committing the patch. Add new streaming overloads and modify some

[jira] Resolved: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=all ] Knut Anders Hatlen resolved DERBY-137: -- Fix Version: 10.2.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks again for the quick review, A B! Committed v2

[jira] Updated: (DERBY-1445) Add new streaming overloads and modify some existing ones.

[ http://issues.apache.org/jira/browse/DERBY-1445?page=all ] Knut Anders Hatlen updated DERBY-1445: -- Attachment: ver3-washed.diff The ver2 and ver3 patches reformatted large portions of otherwise unmodified code. This makes it rather difficult to

[jira] Resolved: (DERBY-1445) Add new streaming overloads and modify some existing ones.

[ http://issues.apache.org/jira/browse/DERBY-1445?page=all ] Knut Anders Hatlen resolved DERBY-1445: --- Fix Version: 10.2.0.0 Resolution: Fixed Thanks! Committed the follow-up patch into trunk with revision 417705. Add new streaming

[jira] Updated: (DERBY-1417) Add new, lengthless overloads to the streaming api

[ http://issues.apache.org/jira/browse/DERBY-1417?page=all ] Knut Anders Hatlen updated DERBY-1417: -- Derby Info: (was: [Patch Available]) Committed 'derby-1417-1a-notImplemented.diff' into trunk with revision 417753. Add new, lengthless

[jira] Commented: (DERBY-822) Client driver: Pre-fetch data on executeQuery()

[ http://issues.apache.org/jira/browse/DERBY-822?page=comments#action_12418258 ] Knut Anders Hatlen commented on DERBY-822: -- Kathey Marsden wrote: 1) Queries may fail earlier. Instead of failing on the ResultSet next() call, they may now

[jira] Resolved: (DERBY-1463) Resolve javadoc warnings in BrokeredCallableStatement40

[ http://issues.apache.org/jira/browse/DERBY-1463?page=all ] Knut Anders Hatlen resolved DERBY-1463: --- Fix Version: 10.2.0.0 Resolution: Fixed Committed revision 417953. Resolve javadoc warnings in BrokeredCallableStatement40

[jira] Commented: (DERBY-1393) PreparedStatement.setObject(Object,int,int) should throw for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1393?page=comments#action_12418457 ] Knut Anders Hatlen commented on DERBY-1393: --- Thanks for the info, Rick! Seems like setObject() with targetSqlType==JAVA_OBJECT should be supported too, then. For

[jira] Updated: (DERBY-1393) PreparedStatement.setObject(Object,int,int) should throw for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1393?page=all ] Knut Anders Hatlen updated DERBY-1393: -- Attachment: derby-1393-v1.diff derby-1393-v1.stat Attached a patch for this issue (derby-1393-v1.diff). Description of the patch:

[jira] Updated: (DERBY-1393) PreparedStatement.setObject(Object,int,int) should throw for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1393?page=all ] Knut Anders Hatlen updated DERBY-1393: -- Derby Info: [Patch Available] PreparedStatement.setObject(Object,int,int) should throw for unsupported types

[jira] Commented: (DERBY-1364) Client driver does not roll back the effects of a stored procedure when incorrectly invoked by executeQuery()/executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1364?page=comments#action_12418650 ] Knut Anders Hatlen commented on DERBY-1364: --- I plan to commit the patch early next week. Please let me know if you have any comments or need more time to review.

[jira] Updated: (DERBY-1468) Server returns data when it receives a QRYROWSET value of zero on an OPNQRY, which doesn't follow DRDA protocol.

[ http://issues.apache.org/jira/browse/DERBY-1468?page=all ] Knut Anders Hatlen updated DERBY-1468: -- Assign To: Knut Anders Hatlen Derby Info: [Regression] Server returns data when it receives a QRYROWSET value of zero on an OPNQRY, which

[jira] Updated: (DERBY-1468) Server returns data when it receives a QRYROWSET value of zero on an OPNQRY, which doesn't follow DRDA protocol.

[ http://issues.apache.org/jira/browse/DERBY-1468?page=all ] Knut Anders Hatlen updated DERBY-1468: -- Attachment: derby-1468-v1.diff derby-1468-v1.stat The attached patch (v1) disables pre-fetching for LMTBLKPRC when QRYROWSET=0.

[jira] Updated: (DERBY-1468) Server returns data when it receives a QRYROWSET value of zero on an OPNQRY, which doesn't follow DRDA protocol.

[ http://issues.apache.org/jira/browse/DERBY-1468?page=all ] Knut Anders Hatlen updated DERBY-1468: -- Derby Info: [Patch Available, Regression] (was: [Regression]) Server returns data when it receives a QRYROWSET value of zero on an OPNQRY,

[jira] Assigned: (DERBY-1427) sysinfo does not write Java SE and JDBC version when running under JDK 1.6

[ http://issues.apache.org/jira/browse/DERBY-1427?page=all ] Knut Anders Hatlen reassigned DERBY-1427: - Assign To: Knut Anders Hatlen sysinfo does not write Java SE and JDBC version when running under JDK 1.6

[jira] Updated: (DERBY-1427) sysinfo does not write Java SE and JDBC version when running under JDK 1.6

[ http://issues.apache.org/jira/browse/DERBY-1427?page=all ] Knut Anders Hatlen updated DERBY-1427: -- Attachment: derby-1427-v1.diff derby-1427-v1.stat The attached patch makes sysinfo print JRE - JDBC: Java SE 6 - JDBC 4.0 when

[jira] Updated: (DERBY-1427) sysinfo does not write Java SE and JDBC version when running under JDK 1.6

[ http://issues.apache.org/jira/browse/DERBY-1427?page=all ] Knut Anders Hatlen updated DERBY-1427: -- Derby Info: [Patch Available] sysinfo does not write Java SE and JDBC version when running under JDK 1.6

[jira] Resolved: (DERBY-1427) sysinfo does not write Java SE and JDBC version when running under JDK 1.6

[ http://issues.apache.org/jira/browse/DERBY-1427?page=all ] Knut Anders Hatlen resolved DERBY-1427: --- Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks, Andrew! Committed revision 418687. sysinfo does not write Java SE and

[jira] Resolved: (DERBY-1468) Server returns data when it receives a QRYROWSET value of zero on an OPNQRY, which doesn't follow DRDA protocol.

[ http://issues.apache.org/jira/browse/DERBY-1468?page=all ] Knut Anders Hatlen resolved DERBY-1468: --- Fix Version: 10.2.0.0 Resolution: Fixed Derby Info: [Regression] (was: [Patch Available, Regression]) Thanks for the review,

[jira] Resolved: (DERBY-1364) Client driver does not roll back the effects of a stored procedure when incorrectly invoked by executeQuery()/executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1364?page=all ] Knut Anders Hatlen resolved DERBY-1364: --- Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 418692. Client driver does not roll back the effects of a

[jira] Commented: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=comments#action_12418941 ] Knut Anders Hatlen commented on DERBY-989: -- I have a hypothesis, but it's hard to verify since the failure is intermittent and the test needs much time to finish. I

[jira] Assigned: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Knut Anders Hatlen reassigned DERBY-989: Assign To: Knut Anders Hatlen unit/daemonService.unit fails intermittently: 'ran out of time'

[jira] Commented: (DERBY-1237) unit/daemonService fails intermittently with Shutting down due to unit test failure.

[ http://issues.apache.org/jira/browse/DERBY-1237?page=comments#action_12418964 ] Knut Anders Hatlen commented on DERBY-1237: --- This could be a duplicate of DERBY-989, but it's hard to say since the real error message is hidden in derby.log.

[jira] Assigned: (DERBY-1237) unit/daemonService fails intermittently with Shutting down due to unit test failure.

[ http://issues.apache.org/jira/browse/DERBY-1237?page=all ] Knut Anders Hatlen reassigned DERBY-1237: - Assign To: Knut Anders Hatlen unit/daemonService fails intermittently with Shutting down due to unit test failure.

[jira] Updated: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Knut Anders Hatlen updated DERBY-989: - Attachment: derby-989-timebomb.diff derby-989-timebomb.stat Attached a one-line patch (derby-989-timebomb.diff) which removes the time

[jira] Updated: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Knut Anders Hatlen updated DERBY-989: - Attachment: derby-989-v1.diff derby-989-v1.stat The attached patch (derby-989-v1.diff) attempts to solve the real problem. Derbyall

[jira] Commented: (DERBY-1237) unit/daemonService fails intermittently with Shutting down due to unit test failure.

[ http://issues.apache.org/jira/browse/DERBY-1237?page=comments#action_12419080 ] Knut Anders Hatlen commented on DERBY-1237: --- I have gone through the logs from these failures in Ole's regression testing:

[jira] Commented: (DERBY-496) unit test 'org.apache.derbyTesting.unitTests.services.T_Diagnosticable' was failed

[ http://issues.apache.org/jira/browse/DERBY-496?page=comments#action_12419150 ] Knut Anders Hatlen commented on DERBY-496: -- I believe this failure has not occurred on trunk after the check-in of DERBY-496_2_addition.patch (revision 278581). If no

[jira] Commented: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=comments#action_12419163 ] Knut Anders Hatlen commented on DERBY-989: -- Thank you Andreas and Bryan for reviewing the patch. Bryan wrote: 1) I don't really see why unsubscribe needs to block

[jira] Commented: (DERBY-1393) PreparedStatement.setObject(Object,int,int) should throw for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1393?page=comments#action_12419166 ] Knut Anders Hatlen commented on DERBY-1393: --- Hi Bryan, 1) The name of the test, (that is, the argument to org.apache.derbyTesting.functionTests.harness.RunTest) is

[jira] Created: (DERBY-1476) PreparedStatement.setNull(int,int) should throw SQLFeatureNotSupportedException for unsupported types

PreparedStatement.setNull(int,int) should throw SQLFeatureNotSupportedException for unsupported types - Key: DERBY-1476 URL: http://issues.apache.org/jira/browse/DERBY-1476

[jira] Updated: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Knut Anders Hatlen updated DERBY-989: - Attachment: derby-989-testfix.diff derby-989-testfix.stat derby-989-testfix.diff is an alternative solution. This patch only changes

[jira] Commented: (DERBY-1248) Assert failure in BasePage.shiftUp() when running store/onlineBackupTest4.sql

[ http://issues.apache.org/jira/browse/DERBY-1248?page=comments#action_12419280 ] Knut Anders Hatlen commented on DERBY-1248: --- I also see this failure on Linux, but not as frequently as on Solaris (had to run the test 125 times on Linux, whereas

[jira] Resolved: (DERBY-1237) unit/daemonService fails intermittently with Shutting down due to unit test failure.

[ http://issues.apache.org/jira/browse/DERBY-1237?page=all ] Knut Anders Hatlen resolved DERBY-1237: --- Resolution: Duplicate This issue is a duplicate of DERBY-989. Fix version is left blank. unit/daemonService fails intermittently with

[jira] Updated: (DERBY-1248) Assert failure in BasePage.shiftUp() when running store/onlineBackupTest4.sql

[ http://issues.apache.org/jira/browse/DERBY-1248?page=all ] Knut Anders Hatlen updated DERBY-1248: -- Attachment: linuxfailure.zip solarisfailure.zip Attaching two new zips. One for a failure on Linux and one for a failure on

[jira] Commented: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=comments#action_12419434 ] Knut Anders Hatlen commented on DERBY-989: -- Thanks for your comments, Suresh! I think I will just fix the test for now since it doesn't seem like the current

[jira] Commented: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=comments#action_12419437 ] Knut Anders Hatlen commented on DERBY-989: -- Committed derby-989-timebomb.diff and derby-989-testfix.diff into trunk with revision 419479. I will also update the

[jira] Created: (DERBY-1481) Client driver: ResultSet.beforeFirst() gives protocol error on scrollable, updatable result sets that are downgraded to read-only

Client driver: ResultSet.beforeFirst() gives protocol error on scrollable, updatable result sets that are downgraded to read-only - Key: DERBY-1481

[jira] Updated: (DERBY-1481) Client driver: ResultSet.beforeFirst() gives protocol error on scrollable, updatable result sets that are downgraded to read-only

[ http://issues.apache.org/jira/browse/DERBY-1481?page=all ] Knut Anders Hatlen updated DERBY-1481: -- Attachment: Repro.java Attached Repro.java which reproduces the error. Client driver: ResultSet.beforeFirst() gives protocol error on scrollable,

[jira] Updated: (DERBY-1474) Add assertEquals overloads for Blob and Clob

[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ] Knut Anders Hatlen updated DERBY-1474: -- Attachment: derby-1474-1c.diff I have reviewed the patch. The methods look very useful. I found one issue: assertEquals(Blob,Blob) has

[jira] Resolved: (DERBY-1474) Add assertEquals overloads for Blob and Clob

[ http://issues.apache.org/jira/browse/DERBY-1474?page=all ] Knut Anders Hatlen resolved DERBY-1474: --- Fix Version: 10.2.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed derby-1474-1c.diff into trunk with

[jira] Commented: (DERBY-1474) Add assertEquals overloads for Blob and Clob

[ http://issues.apache.org/jira/browse/DERBY-1474?page=comments#action_12419589 ] Knut Anders Hatlen commented on DERBY-1474: --- Hi Kristian, I think your approach is good. I have a couple of comments about your BaseTestCase.generateError() method.

[jira] Commented: (DERBY-1474) Add assertEquals overloads for Blob and Clob

[ http://issues.apache.org/jira/browse/DERBY-1474?page=comments#action_12419669 ] Knut Anders Hatlen commented on DERBY-1474: --- Committed derby-1474-2b.diff into trunk with revision 419848. Add assertEquals overloads for Blob and Clob

[jira] Updated: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Knut Anders Hatlen updated DERBY-989: - Attachment: derby-989-javadoc.diff derby-989-javadoc.stat Attaching a patch which updates the javadoc for DaemonService and

[jira] Resolved: (DERBY-1000) For LDAP authentication: derby.authentication.server should support ldaps:// as part of the server url.

[ http://issues.apache.org/jira/browse/DERBY-1000?page=all ] Knut Anders Hatlen resolved DERBY-1000: --- Fix Version: 10.2.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) I think the doc patch is ready to be committed too.

[jira] Updated: (DERBY-1248) Assert failure in BasePage.shiftUp() when running store/onlineBackupTest4.sql

[ http://issues.apache.org/jira/browse/DERBY-1248?page=all ] Knut Anders Hatlen updated DERBY-1248: -- Attachment: solaris-singlecpu.zip Now I have seen this failure on a single-CPU machine as well. I was running derbyall on a Pentium 4, 2.66 GHz,

[jira] Commented: (DERBY-1393) PreparedStatement.setObject(Object,int,int) should throw for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1393?page=comments#action_12419689 ] Knut Anders Hatlen commented on DERBY-1393: --- Hi Bryan, did you have more comments to the patch? If not, I plan to commit it next week. Thanks!

[jira] Commented: (DERBY-1274) Network Server does not shutdown the databases it has booted when started and shutdown from the command line

[ http://issues.apache.org/jira/browse/DERBY-1274?page=comments#action_12419694 ] Knut Anders Hatlen commented on DERBY-1274: --- Hi Fernanda, If I understand your patch correctly, using NetworkServerControl from version 10.2 to stop a 10.1 network

[jira] Created: (DERBY-1484) Client and embedded behave differently when the table name is null in DatabaseMetaData methods

Client and embedded behave differently when the table name is null in DatabaseMetaData methods -- Key: DERBY-1484 URL: http://issues.apache.org/jira/browse/DERBY-1484 Project: Derby

[jira] Updated: (DERBY-1248) Assert failure in BasePage.shiftUp() when running store/onlineBackupTest4.sql

[ http://issues.apache.org/jira/browse/DERBY-1248?page=all ] Knut Anders Hatlen updated DERBY-1248: -- Attachment: test5.zip Attached 'test5.zip' which contains logs/db from a failure in OnlineBackupTest5.sql. Assert failure in BasePage.shiftUp()

[jira] Updated: (DERBY-1393) PreparedStatement.setObject(int,Object,int) should throw SQLFeatureNotSupportedException for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1393?page=all ] Knut Anders Hatlen updated DERBY-1393: -- Summary: PreparedStatement.setObject(int,Object,int) should throw SQLFeatureNotSupportedException for unsupported types (was:

[jira] Resolved: (DERBY-1393) PreparedStatement.setObject(int,Object,int) should throw SQLFeatureNotSupportedException for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1393?page=all ] Knut Anders Hatlen resolved DERBY-1393: --- Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks Bryan! Committed revision 420436.

[jira] Closed: (DERBY-1364) Client driver does not roll back the effects of a stored procedure when incorrectly invoked by executeQuery()/executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1364?page=all ] Knut Anders Hatlen closed DERBY-1364: - Client driver does not roll back the effects of a stored procedure when incorrectly invoked by executeQuery()/executeUpdate()

[jira] Closed: (DERBY-1039) Database creation should fail if specified log device path already exists

[ http://issues.apache.org/jira/browse/DERBY-1039?page=all ] Knut Anders Hatlen closed DERBY-1039: - Database creation should fail if specified log device path already exists

[jira] Created: (DERBY-1493) EmbeddedDriver does not implement PreparedStatement.setNull(int, int, String)

EmbeddedDriver does not implement PreparedStatement.setNull(int, int, String) - Key: DERBY-1493 URL: http://issues.apache.org/jira/browse/DERBY-1493 Project: Derby Type: Bug Components:

[jira] Updated: (DERBY-1493) EmbeddedDriver does not implement PreparedStatement.setNull(int, int, String)

[ http://issues.apache.org/jira/browse/DERBY-1493?page=all ] Knut Anders Hatlen updated DERBY-1493: -- Description: The embedded driver throws Util.notImplemented() when PreparedStatement.setNull(int, int, String) is called. The javadoc says that

[jira] Created: (DERBY-1494) PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client

PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client Key: DERBY-1494 URL: http://issues.apache.org/jira/browse/DERBY-1494 Project:

[jira] Commented: (DERBY-1494) PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client

[ http://issues.apache.org/jira/browse/DERBY-1494?page=comments#action_12420005 ] Knut Anders Hatlen commented on DERBY-1494: --- Although both implementations of setNull(int,int) are compliant, I think it would make more sense to change the

[jira] Resolved: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Knut Anders Hatlen resolved DERBY-989: -- Fix Version: 10.2.0.0 Resolution: Fixed Thank you for looking at the patch, Bryan! Committed 'derby-989-javadoc.diff' into trunk with

[jira] Commented: (DERBY-1330) Provide runtime privilege checking for grant/revoke functionality

[ http://issues.apache.org/jira/browse/DERBY-1330?page=comments#action_12420027 ] Knut Anders Hatlen commented on DERBY-1330: --- I have seen this regression test failure a couple of times lately. Could it be related to this issue? * Diff

[jira] Commented: (DERBY-1417) Add new, lengthless overloads to the streaming api

[ http://issues.apache.org/jira/browse/DERBY-1417?page=comments#action_12420034 ] Knut Anders Hatlen commented on DERBY-1417: --- derby-1417-2a-rstest-refactor.diff looks good. Committed revision 420497. Add new, lengthless overloads to the

[jira] Updated: (DERBY-1476) PreparedStatement.setNull(int,int) should throw SQLFeatureNotSupportedException for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1476?page=all ] Knut Anders Hatlen updated DERBY-1476: -- Attachment: derby-1476-v1.diff derby-1476-v1.stat derby-1476-v1.diff adds a call to checkForSupportedDataType() in setNull(). It

[jira] Updated: (DERBY-1476) PreparedStatement.setNull(int,int) should throw SQLFeatureNotSupportedException for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1476?page=all ] Knut Anders Hatlen updated DERBY-1476: -- Derby Info: [Patch Available] PreparedStatement.setNull(int,int) should throw SQLFeatureNotSupportedException for unsupported types

[jira] Resolved: (DERBY-1502) Non-deterministic behavior of lang/grantRevokeDDL.sql

[ http://issues.apache.org/jira/browse/DERBY-1502?page=all ] Knut Anders Hatlen resolved DERBY-1502: --- Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks Mamta! Committed revision 421179. Non-deterministic behavior of

[jira] Commented: (DERBY-1501) PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY in embedded mode

[ http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12420549 ] Knut Anders Hatlen commented on DERBY-1501: --- Kristian wrote: But what about the second issue? The embedded driver determines if the type of the parameter is

[jira] Created: (DERBY-1503) Make jdbc4/StatementEventsTest.junit test callable statements

Make jdbc4/StatementEventsTest.junit test callable statements - Key: DERBY-1503 URL: http://issues.apache.org/jira/browse/DERBY-1503 Project: Derby Type: Improvement Components: JDBC, Test

[jira] Updated: (DERBY-1503) Make jdbc4/StatementEventsTest.junit test callable statements

[ http://issues.apache.org/jira/browse/DERBY-1503?page=all ] Knut Anders Hatlen updated DERBY-1503: -- Attachment: derby-1503-v1.diff The attached patch changes StatementEventsTest the following way: 1) New methods setXA() and setCallable() which

[jira] Closed: (DERBY-1503) Make jdbc4/StatementEventsTest.junit test callable statements

[ http://issues.apache.org/jira/browse/DERBY-1503?page=all ] Knut Anders Hatlen closed DERBY-1503: - Fix Version: 10.2.0.0 Resolution: Fixed Committed revision 421218. Make jdbc4/StatementEventsTest.junit test callable statements

[jira] Commented: (DERBY-323) Locale problem in test of derby

[ http://issues.apache.org/jira/browse/DERBY-323?page=comments#action_12420598 ] Knut Anders Hatlen commented on DERBY-323: -- The DERBY-1352 fix didn't completely fix this issue. When I ran derbyall with Japanese locale, the nist tests and some

[jira] Closed: (DERBY-1476) PreparedStatement.setNull(int,int) should throw SQLFeatureNotSupportedException for unsupported types

[ http://issues.apache.org/jira/browse/DERBY-1476?page=all ] Knut Anders Hatlen closed DERBY-1476: - Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 421255. PreparedStatement.setNull(int,int) should throw

  1   2   3   4   5   6   7   8   9   10   >