[jira] Created: (DERBY-748) Should document the default schemas in a newly created database

Should document the default schemas in a newly created database --- Key: DERBY-748 URL: http://issues.apache.org/jira/browse/DERBY-748 Project: Derby Type: Improvement Components: Documentation

[jira] Updated: (DERBY-297) Submit an entry for the Derby logo contest by uploading it to this issue

[ http://issues.apache.org/jira/browse/DERBY-297?page=all ] Oyvind Bakksjo updated DERBY-297: - Attachment: derbyhatlogo-lettersaligned.png Maybe someone who's more skilled with graphics than I am can take the hat idea, place all the characters on the

[jira] Created: (DERBY-710) Building the documentation as pdf stops with OutOfMemoryError

Building the documentation as pdf stops with OutOfMemoryError - Key: DERBY-710 URL: http://issues.apache.org/jira/browse/DERBY-710 Project: Derby Type: Bug Components: Build tools Environment: Head of

[jira] Commented: (DERBY-31) Statement.setQueryTimeout() support.

[ http://issues.apache.org/jira/browse/DERBY-31?page=comments#action_12357683 ] Oyvind Bakksjo commented on DERBY-31: - Updated documentation which stated setQueryTimeout was not implemented. Sendingsrc/ref/rrefjdbc40794.dita Transmitting file

[jira] Updated: (DERBY-31) Statement.setQueryTimeout() support.

[ http://issues.apache.org/jira/browse/DERBY-31?page=all ] Oyvind Bakksjo updated DERBY-31: Comment: was deleted Statement.setQueryTimeout() support. Key: DERBY-31 URL:

[jira] Created: (DERBY-708) Client driver truncates database names with spaces

Client driver truncates database names with spaces -- Key: DERBY-708 URL: http://issues.apache.org/jira/browse/DERBY-708 Project: Derby Type: Bug Components: Network Client Versions: 10.1.1.2 Reporter:

[jira] Commented: (DERBY-506) Implement Statement.setQueryTimeout in the Client Driver

[ http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12357597 ] Oyvind Bakksjo commented on DERBY-506: -- Sendingjava/client/org/apache/derby/client/am/PreparedStatement.java Sending

[jira] Resolved: (DERBY-506) Implement Statement.setQueryTimeout in the Client Driver

[ http://issues.apache.org/jira/browse/DERBY-506?page=all ] Oyvind Bakksjo resolved DERBY-506: -- Resolution: Fixed Had to disable some testing because of DERBY-694 Implement Statement.setQueryTimeout in the Client Driver

[jira] Closed: (DERBY-506) Implement Statement.setQueryTimeout in the Client Driver

[ http://issues.apache.org/jira/browse/DERBY-506?page=all ] Oyvind Bakksjo closed DERBY-506: Implement Statement.setQueryTimeout in the Client Driver Key: DERBY-506 URL:

[jira] Created: (DERBY-705) Re-enable test which was disabled in DERBY-506 commit

Re-enable test which was disabled in DERBY-506 commit - Key: DERBY-705 URL: http://issues.apache.org/jira/browse/DERBY-705 Project: Derby Type: Test Components: Test Reporter: Oyvind Bakksjo Priority:

[jira] Updated: (DERBY-506) Implement Statement.setQueryTimeout in the Client Driver

[ http://issues.apache.org/jira/browse/DERBY-506?page=all ] Oyvind Bakksjo updated DERBY-506: - Attachment: (was: DERBY-506_PRE.diff) Implement Statement.setQueryTimeout in the Client Driver

[jira] Updated: (DERBY-506) Implement Statement.setQueryTimeout in the Client Driver

[ http://issues.apache.org/jira/browse/DERBY-506?page=all ] Oyvind Bakksjo updated DERBY-506: - Attachment: DERBY-506.status Implement Statement.setQueryTimeout in the Client Driver

[jira] Updated: (DERBY-506) Implement Statement.setQueryTimeout in the Client Driver

[ http://issues.apache.org/jira/browse/DERBY-506?page=all ] Oyvind Bakksjo updated DERBY-506: - Attachment: DERBY-506.diff Diff from revision 332067. Implement Statement.setQueryTimeout in the Client Driver

[jira] Created: (DERBY-694) Statement exceptions cause all the connection's result sets to be closed with the client driver

Statement exceptions cause all the connection's result sets to be closed with the client driver --- Key: DERBY-694 URL: http://issues.apache.org/jira/browse/DERBY-694 Project: Derby

[jira] Updated: (DERBY-694) Statement exceptions cause all the connection's result sets to be closed with the client driver

[ http://issues.apache.org/jira/browse/DERBY-694?page=all ] Oyvind Bakksjo updated DERBY-694: - Attachment: StatementRollbackTest.java Attached program which demonstrates the bug. Statement exceptions cause all the connection's result sets to be closed

[jira] Resolved: (DERBY-663) Test of derby fails because difference in encoding of eol make sizes of test data files different between platforms.

[ http://issues.apache.org/jira/browse/DERBY-663?page=all ] Oyvind Bakksjo resolved DERBY-663: -- Fix Version: 10.2.0.0 Resolution: Fixed Test of derby fails because difference in encoding of eol make sizes of test data files different

[jira] Commented: (DERBY-663) Test of derby fails because difference in encoding of eol make sizes of test data files different between platforms.

[ http://issues.apache.org/jira/browse/DERBY-663?page=comments#action_12356634 ] Oyvind Bakksjo commented on DERBY-663: -- Sending java/testing/org/apache/derbyTesting/functionTests/testData/ImportExport/position_info.del Transmitting file data .

[jira] Commented: (DERBY-663) Test of derby fails because difference in encoding of eol make sizes of test data files different between platforms.

[ http://issues.apache.org/jira/browse/DERBY-663?page=comments#action_12356502 ] Oyvind Bakksjo commented on DERBY-663: -- Sending java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/aclob.txt Sending

[jira] Commented: (DERBY-506) Implement Statement.setQueryTimeout in the Client Driver

[ http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12331714 ] Oyvind Bakksjo commented on DERBY-506: -- Sending the EXCSQLSET when the JDBC call [to Statement.setQueryTimeout()] is made would cause an additional round-trip between the

[jira] Commented: (DERBY-506) Implement Statement.setQueryTimeout in the Client Driver

[ http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12331738 ] Oyvind Bakksjo commented on DERBY-506: -- I understand your points, but with regards to setQueryTimeout(), I honestly think you're making too much of this. ;-) To make my

[jira] Updated: (DERBY-506) Implement Statement.setQueryTimeout in the Client Driver

[ http://issues.apache.org/jira/browse/DERBY-506?page=all ] Oyvind Bakksjo updated DERBY-506: - Attachment: DERBY-506_PRE.diff This patch is not intended for inclusion, it just illustrates the idea and is a basis for discussion about the approach. The

[jira] Resolved: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

[ http://issues.apache.org/jira/browse/DERBY-579?page=all ] Oyvind Bakksjo resolved DERBY-579: -- Resolution: Fixed Query timeout set for one statement may affect other statements with the same SQL string

[jira] Commented: (DERBY-587) Providing JDBC 4.0 support for derby

[ http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12331272 ] Oyvind Bakksjo commented on DERBY-587: -- OK, I'll commit it. Providing JDBC 4.0 support for derby Key: DERBY-587

[jira] Updated: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

[ http://issues.apache.org/jira/browse/DERBY-579?page=all ] Oyvind Bakksjo updated DERBY-579: - Attachment: (was: DERBY-579.svn.diff) Query timeout set for one statement may affect other statements with the same SQL string

[jira] Updated: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

[ http://issues.apache.org/jira/browse/DERBY-579?page=all ] Oyvind Bakksjo updated DERBY-579: - Attachment: (was: DERBY-579.svn.status) Query timeout set for one statement may affect other statements with the same SQL string

[jira] Updated: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

[ http://issues.apache.org/jira/browse/DERBY-579?page=all ] Oyvind Bakksjo updated DERBY-579: - Attachment: DERBY-579.svn.status Query timeout set for one statement may affect other statements with the same SQL string

[jira] Commented: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

[ http://issues.apache.org/jira/browse/DERBY-579?page=comments#action_12331188 ] Oyvind Bakksjo commented on DERBY-579: -- Last attached diff relates to svn repository version 293374. Query timeout set for one statement may affect other statements with

[jira] Created: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

Query timeout set for one statement may affect other statements with the same SQL string Key: DERBY-579 URL: http://issues.apache.org/jira/browse/DERBY-579 Project: Derby Type:

[jira] Updated: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

[ http://issues.apache.org/jira/browse/DERBY-579?page=all ] Oyvind Bakksjo updated DERBY-579: - Attachment: DERBY-579.svn.status Query timeout set for one statement may affect other statements with the same SQL string

[jira] Updated: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

[ http://issues.apache.org/jira/browse/DERBY-579?page=all ] Oyvind Bakksjo updated DERBY-579: - Attachment: DERBY-579.svn.diff This patch fixes the bug as proposed by Dan Debrunner (pass the timeout into the execute method of

[jira] Closed: (DERBY-574) Per JDBC connection timeouts are incorrectly set on org.apache.derby.iapi.sql.PreparedStatement which represents a shared plan.

[ http://issues.apache.org/jira/browse/DERBY-574?page=all ] Oyvind Bakksjo closed DERBY-574: Fix Version: (was: 10.2.0.0) Resolution: Duplicate Per JDBC connection timeouts are incorrectly set on

[jira] Closed: (DERBY-544) Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS

[ http://issues.apache.org/jira/browse/DERBY-544?page=all ] Oyvind Bakksjo closed DERBY-544: Resolution: Fixed Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS ---

[jira] Commented: (DERBY-544) Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS

[ http://issues.apache.org/jira/browse/DERBY-544?page=comments#action_12322775 ] Oyvind Bakksjo commented on DERBY-544: -- I'll go ahead and commit it. Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS

[jira] Created: (DERBY-544) Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS

Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS --- Key: DERBY-544 URL: http://issues.apache.org/jira/browse/DERBY-544 Project: Derby Type: Bug Components: Documentation Versions:

[jira] Updated: (DERBY-544) Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS

[ http://issues.apache.org/jira/browse/DERBY-544?page=all ] Oyvind Bakksjo updated DERBY-544: - Attachment: DERBY-544.diff DERBY-544.status Admin guide has wrong value for constant TRACE_RESULT_SET_CALLS

[jira] Resolved: (DERBY-463) Successive writes to a java.sql.Blob.setBinaryStream(long) seem to reset the file pointer

[ http://issues.apache.org/jira/browse/DERBY-463?page=all ] Oyvind Bakksjo resolved DERBY-463: -- Fix Version: 10.2.0.0 Resolution: Fixed Committed revision 233487. Successive writes to a java.sql.Blob.setBinaryStream(long) seem to reset the

[jira] Closed: (DERBY-505) Add system procedure to allow setting statement timeout

[ http://issues.apache.org/jira/browse/DERBY-505?page=all ] Oyvind Bakksjo closed DERBY-505: Resolution: Won't Fix No interest in this functionality. Use JDBC instead. Add system procedure to allow setting statement timeout

[jira] Commented: (DERBY-463) Successive writes to a java.sql.Blob.setBinaryStream(long) seem to reset the file pointer

[ http://issues.apache.org/jira/browse/DERBY-463?page=comments#action_12319005 ] Oyvind Bakksjo commented on DERBY-463: -- The bugfix looks ok. My comments do not concern the fix, but the patch itself: - BlobOutputStream.java: The System.arraycopy()

[jira] Created: (DERBY-503) Documentation should recommend using .newInstance() to instantiate JDBC driver

Documentation should recommend using .newInstance() to instantiate JDBC driver -- Key: DERBY-503 URL: http://issues.apache.org/jira/browse/DERBY-503 Project: Derby Type: Improvement

[jira] Created: (DERBY-505) Add system procedure to allow setting statement timeout

Add system procedure to allow setting statement timeout --- Key: DERBY-505 URL: http://issues.apache.org/jira/browse/DERBY-505 Project: Derby Type: New Feature Components: SQL Versions: 10.1.1.0

[jira] Created: (DERBY-506) Implement Statement.setQueryTimeout in the Client Driver

Implement Statement.setQueryTimeout in the Client Driver Key: DERBY-506 URL: http://issues.apache.org/jira/browse/DERBY-506 Project: Derby Type: New Feature Components: JDBC Versions: 10.1.1.0

[jira] Commented: (DERBY-31) Statement.setQueryTimeout() support.

[ http://issues.apache.org/jira/browse/DERBY-31?page=comments#action_12313431 ] Oyvind Bakksjo commented on DERBY-31: - Hi Dan, thanks for reviewing this patch so quickly. I am fully aware of and share you concern for the performance impact of creating

[jira] Updated: (DERBY-31) Statement.setQueryTimeout() support.

[ http://issues.apache.org/jira/browse/DERBY-31?page=all ] Oyvind Bakksjo updated DERBY-31: Attachment: svn.diff Output of the 'svn diff' command. Statement.setQueryTimeout() support. Key: DERBY-31

[jira] Updated: (DERBY-31) Statement.setQueryTimeout() support.

[ http://issues.apache.org/jira/browse/DERBY-31?page=all ] Oyvind Bakksjo updated DERBY-31: Attachment: svn.status Output of the 'svn status' command. Statement.setQueryTimeout() support. Key: DERBY-31

[jira] Assigned: (DERBY-31) Statement.setQueryTimeout() support.

[ http://issues.apache.org/jira/browse/DERBY-31?page=all ] Oyvind Bakksjo reassigned DERBY-31: --- Assign To: Oyvind Bakksjo Statement.setQueryTimeout() support. Key: DERBY-31 URL: