Re: catch-22: Derby, Mustang, and JCP issue

True. But we're not talking about just anybody. If a member of the Derby community does put together a release candidate (that would need to report itself as a GA version) and publishes it on a website for others to vote on, then the community could be held responsible. For what? As far as

[jira] Updated: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=all ] Andreas Korneliussen updated DERBY-1361: Attachment: DERBY-1361v2.diff DERBY-1361v2.stat Attaching an updated patch. Two more master files had to be updated because

Re: [VOTE] 10.1.3.0 release

+1 Based on test results: http://www.multinet.no/~solberg/public/Apache/index.html Andreas

[jira] Commented: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=comments#action_12417059 ] Andreas Korneliussen commented on DERBY-1361: - For the scrollable case, I found two problems: 1. The network client will do a parsing of the SQL and reposition

[jira] Commented: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=comments#action_12417072 ] Andreas Korneliussen commented on DERBY-1361: - BTW, this is what SQL foundation, part 2, 4.29 Cursors, says about this situation: A holdable cursor that has been

[jira] Updated: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=all ] Andreas Korneliussen updated DERBY-1361: Attachment: DERBY-1361.diff DERBY-1361.stat Attaching a patch for this issue. The patch (DERBY-1361.diff + stat) does

[jira] Resolved: (DERBY-1374) compatibility test fails with 'PROTOCOL Data Stream Syntax Error'

[ http://issues.apache.org/jira/browse/DERBY-1374?page=all ] Andreas Korneliussen resolved DERBY-1374: - Resolution: Fixed Committed revision 415557. compatibility test fails with 'PROTOCOL Data Stream Syntax Error

[jira] Commented: (DERBY-1374) compatibility test fails with 'PROTOCOL Data Stream Syntax Error'

[ http://issues.apache.org/jira/browse/DERBY-1374?page=comments#action_12416770 ] Andreas Korneliussen commented on DERBY-1374: - I will run tests on the patch and commit it. compatibility test fails with 'PROTOCOL Data Stream Syntax Error

[jira] Commented: (DERBY-1382) client: lobs fails silently with result sets of type TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-1382?page=comments#action_12416157 ] Andreas Korneliussen commented on DERBY-1382: - Committed revision 414165. client: lobs fails silently with result sets of type TYPE_SCROLL_INSENSITIVE

[jira] Updated: (DERBY-1382) client: lobs fails silently with result sets of type TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-1382?page=all ] Andreas Korneliussen updated DERBY-1382: Derby Info: (was: [Patch Available]) Committed revision 414179 (doc) All patches committed, clearing patch available flag. Please resolve

[jira] Commented: (DERBY-1408) derbyall/jdbcapi/ScrollResultSetTest failed

[ http://issues.apache.org/jira/browse/DERBY-1408?page=comments#action_12416175 ] Andreas Korneliussen commented on DERBY-1408: - I think the test should not run on JDK 1.3, since it uses ResultSet.setHoldability(..) Is there any more

[jira] Commented: (DERBY-1408) derbyall/jdbcapi/ScrollResultSetTest failed

[ http://issues.apache.org/jira/browse/DERBY-1408?page=comments#action_12416183 ] Andreas Korneliussen commented on DERBY-1408: - Comment by Mike Matrigali [14/Jun/06 12:25 AM] This failed in the 6/9 build and passed in this environment on 6/2

[jira] Commented: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=comments#action_12416186 ] Andreas Korneliussen commented on DERBY-1361: - I am following the proposal outlined above. As part of testing my changes, I found that Derby offers two different

[jira] Updated: (DERBY-717) update doc on updatable cursors

[ http://issues.apache.org/jira/browse/DERBY-717?page=all ] Andreas Korneliussen updated DERBY-717: --- Description: The new features introduced in DERBY-690, DERBY-231, DERBY-775 and DERBY-100 should be documented in the Derby documentation

[jira] Resolved: (DERBY-717) update doc on updatable cursors

[ http://issues.apache.org/jira/browse/DERBY-717?page=all ] Andreas Korneliussen resolved DERBY-717: Fix Version: 10.2.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 413877. update doc

[jira] Resolved: (DERBY-1385) update reference manual: scrollable insensitive resultsets will no longer be closed implicitly after a next

[ http://issues.apache.org/jira/browse/DERBY-1385?page=all ] Andreas Korneliussen resolved DERBY-1385: - Fix Version: 10.2.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 413886. update reference

Re: Patch available flag

Kristian Waagan wrote: Hello all, I'm a bit confused about the 'Patch available' flag. I believed it was not supposed to be unset when a patch was committed, unless the patch was partial. I also thought the filter that has been created for finding issues ready to review/commit filtered on

[jira] Commented: (DERBY-1382) client: lobs fails silently with result sets of type TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-1382?page=comments#action_12416017 ] Andreas Korneliussen commented on DERBY-1382: - Patch looks good. I will run tests and commit. client: lobs fails silently with result sets of type

[jira] Commented: (DERBY-1384) Increase default BLOB/CLOB length to maximum supported (2G?)

[ http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415856 ] Andreas Korneliussen commented on DERBY-1384: - This is the case I was thinking about. I have coded my application without specifying lengths for BLOB/CLOB. I

[jira] Commented: (DERBY-1058) derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.

[ http://issues.apache.org/jira/browse/DERBY-1058?page=comments#action_12415543 ] Andreas Korneliussen commented on DERBY-1058: - The problem reported has been reproduced on the 10.1.3 After applying the patch in DERBY-1087.diff and recompiling

[jira] Commented: (DERBY-1058) derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.

[ http://issues.apache.org/jira/browse/DERBY-1058?page=comments#action_12415594 ] Andreas Korneliussen commented on DERBY-1058: - One test failed. Do not know if it is related to the fix (have not analyzed it) * Diff file derbyall/unit

Re: [jira] Commented: (DERBY-1058) derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.

Knut Anders Hatlen wrote: Andreas Korneliussen (JIRA) derby-dev@db.apache.org writes: [ http://issues.apache.org/jira/browse/DERBY-1058?page=comments#action_12415594 ] Andreas Korneliussen commented on DERBY-1058: - One test failed. Do

[jira] Resolved: (DERBY-1058) derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.

[ http://issues.apache.org/jira/browse/DERBY-1058?page=all ] Andreas Korneliussen resolved DERBY-1058: - Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 413150. derby fails supporting holdable scrollable

[jira] Closed: (DERBY-1058) derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.

[ http://issues.apache.org/jira/browse/DERBY-1058?page=all ] Andreas Korneliussen closed DERBY-1058: --- derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed

[jira] Commented: (DERBY-1295) Result sets of type TYPE_SCROLL_INSENSITIVE should not implicitly close due to positioning in autocommit mode

[ http://issues.apache.org/jira/browse/DERBY-1295?page=comments#action_12415306 ] Andreas Korneliussen commented on DERBY-1295: - Patch looks good - I will run some test and commit if successful. Result sets of type TYPE_SCROLL_INSENSITIVE

[jira] Commented: (DERBY-1295) Result sets of type TYPE_SCROLL_INSENSITIVE should not implicitly close due to positioning in autocommit mode

[ http://issues.apache.org/jira/browse/DERBY-1295?page=comments#action_12415329 ] Andreas Korneliussen commented on DERBY-1295: - Some preliminary testing results: * When running the new test, without the patch, the test failed as expected

[jira] Updated: (DERBY-1295) Result sets of type TYPE_SCROLL_INSENSITIVE should not implicitly close due to positioning in autocommit mode

[ http://issues.apache.org/jira/browse/DERBY-1295?page=all ] Andreas Korneliussen updated DERBY-1295: Attachment: derby-1295v3.diff derby-1295v3.stat Attaching patch derby-1295 with minor update of testcode as commented above

[jira] Commented: (DERBY-1384) Increase default BLOB/CLOB length to maximum supported (2G?)

[ http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415347 ] Andreas Korneliussen commented on DERBY-1384: - Maybe the Release Note Required checkbox should be checked for this change. My understanding is that after

[jira] Commented: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=comments#action_12415365 ] Andreas Korneliussen commented on DERBY-1361: - It seems to me that it is the store layer which has the knowledge on if a cursor has lost its position

[jira] Commented: (DERBY-1384) Increase default BLOB/CLOB length to maximum supported (2G?)

[ http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415394 ] Andreas Korneliussen commented on DERBY-1384: - I do not see how the improvement would cause any problems after an downgrade, since it is about changing

[jira] Resolved: (DERBY-1295) Result sets of type TYPE_SCROLL_INSENSITIVE should not implicitly close due to positioning in autocommit mode

[ http://issues.apache.org/jira/browse/DERBY-1295?page=all ] Andreas Korneliussen resolved DERBY-1295: - Resolution: Fixed Derby Info: [Existing Application Impact, Release Note Needed] (was: [Patch Available, Existing Application

[jira] Created: (DERBY-1385) update reference manual: scrollable insensitive resultsets will no longer be closed implicitly after a next

/DERBY-1385 Project: Derby Type: Sub-task Components: Documentation Versions: 10.2.0.0 Reporter: Andreas Korneliussen Priority: Minor Remove note from reference manual: src/ref/rrefjdbc77156.dita) Note: When working with scrolling insensitive ResultSets when auto

[jira] Commented: (DERBY-1295) Result sets of type TYPE_SCROLL_INSENSITIVE should not implicitly close due to positioning in autocommit mode

[ http://issues.apache.org/jira/browse/DERBY-1295?page=comments#action_12415143 ] Andreas Korneliussen commented on DERBY-1295: - Thanks for contributing this patch. I have added a subtask to fix the documentation issue. Here are some minor

[jira] Assigned: (DERBY-1362) Class-Path manifest entry for derby.jar is missing from the 10.2.0.2 snapshot

[ http://issues.apache.org/jira/browse/DERBY-1362?page=all ] Andreas Korneliussen reassigned DERBY-1362: --- Assign To: Andreas Korneliussen Class-Path manifest entry for derby.jar is missing from the 10.2.0.2 snapshot

[jira] Assigned: (DERBY-1362) Class-Path manifest entry for derby.jar is missing from the 10.2.0.2 snapshot

[ http://issues.apache.org/jira/browse/DERBY-1362?page=all ] Andreas Korneliussen reassigned DERBY-1362: --- Assign To: (was: Andreas Korneliussen) Class-Path manifest entry for derby.jar is missing from the 10.2.0.2 snapshot

[jira] Assigned: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=all ] Andreas Korneliussen reassigned DERBY-1361: --- Assign To: Andreas Korneliussen positioned updates and deletes allowed after a commit without repositioning the cursor - if the table

[jira] Created: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

-1361 URL: http://issues.apache.org/jira/browse/DERBY-1361 Project: Derby Type: Bug Components: JDBC Versions: 10.2.0.0 Environment: Java 1.4 Reporter: Andreas Korneliussen After a commit, the cursor should be positioned before the next row (not on a row

[jira] Commented: (DERBY-1308) Tests jdbcapi/HoldabilityTest.junit, jdbcapi/UpdateXXXTest.junit,jdbcapi/SURTest.junit fail on wctme5.7_foundation

[ http://issues.apache.org/jira/browse/DERBY-1308?page=comments#action_12413781 ] Andreas Korneliussen commented on DERBY-1308: - The patch looks good. I have tested it on the jdbc40 test suite, and got no failures in the junit tests. A minor

Re: junit tests; get*DataSource* methods in BaseJDBCTestCase causing trouble...

Myrna van Lunteren wrote: Hi, With revision 389780 some methods were added into BaseJDBCTestCase.java: DERBY-1157: Helper methods in BaseJDBCTestCase for creating data sources Adding getDataSource(), getConnectionPoolDataSource() and getXADataSource() to BaseJDBCTestCase. The new methods call

Re: [jira] Commented: (DERBY-717) update doc on updatable cursors

I agree this could be improved. My view is that ResultSet is a Java programming interface which gives access to a SQL concept (cursor), so result sets are based on cursors, not opposite. Some existing docs have the opposite view (cursors are defined in terms of ResultSets). In which direction

Re: junit tests; get*DataSource* methods in BaseJDBCTestCase causing trouble...

Knut Anders Hatlen wrote: Myrna van Lunteren [EMAIL PROTECTED] writes: Hi, With revision 389780 some methods were added into BaseJDBCTestCase.java: DERBY-1157: Helper methods in BaseJDBCTestCase for creating data sources Adding getDataSource(), getConnectionPoolDataSource() and

[jira] Commented: (DERBY-717) update doc on updatable cursors

[ http://issues.apache.org/jira/browse/DERBY-717?page=comments#action_12413092 ] Andreas Korneliussen commented on DERBY-717: Thanks for the reviewing. I think I will limit the scope of the first doc patch to the reference guide

[jira] Commented: (DERBY-717) update doc on updatable cursors

[ http://issues.apache.org/jira/browse/DERBY-717?page=comments#action_12413095 ] Andreas Korneliussen commented on DERBY-717: Forward only updatable result sets - Headings in the Dev. Guide are not consistent with respect to ResultSets vs

edit my own comments in JIRA

I would like to be able to edit my own comments in JIRA. Now, I have to make a new comment when I want to correct a spelling mistake or other minor/major errors (i.e misunderstandings etc). The result of not being able to edit my own comments is that JIRA reports may become quite unreadable,

[jira] Closed: (DERBY-1276) Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be populated

[ http://issues.apache.org/jira/browse/DERBY-1276?page=all ] Andreas Korneliussen closed DERBY-1276: --- Thanks for committing. Closing this report since it is a minor issue, which is resolved on 10.2 trunk. If anyone want to port it to the 10.1.3

[jira] Commented: (DERBY-1308) Tests jdbcapi/HoldabilityTest.junit, jdbcapi/UpdateXXXTest.junit,jdbcapi/SURTest.junit fail on wctme5.7_foundation

[ http://issues.apache.org/jira/browse/DERBY-1308?page=comments#action_12413127 ] Andreas Korneliussen commented on DERBY-1308: - I think you may have forgotten to add the new file SubBaseJDBCTestCase using svn add, so it is not showing up

[jira] Commented: (DERBY-1308) Tests jdbcapi/HoldabilityTest.junit, jdbcapi/UpdateXXXTest.junit,jdbcapi/SURTest.junit fail on wctme5.7_foundation

[ http://issues.apache.org/jira/browse/DERBY-1308?page=comments#action_12413162 ] Andreas Korneliussen commented on DERBY-1308: - |What was happening is that after the contribution of adding a number of methods returning these various

[jira] Closed: (DERBY-1249) cursor operation conflict incorrectly handled in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1249?page=all ] Andreas Korneliussen closed DERBY-1249: --- Fix Version: 10.2.0.0 Resolution: Fixed Fixed as part of DERBY-1251. Closing bug as fixed. cursor operation conflict incorrectly

[jira] Closed: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=all ] Andreas Korneliussen closed DERBY-1251: --- Thanks for committing this patch. Closing the report. cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable

[jira] Commented: (DERBY-1087) Updatable result sets behave different depending on the type of query used to generate the result set

[ http://issues.apache.org/jira/browse/DERBY-1087?page=comments#action_12379028 ] Andreas Korneliussen commented on DERBY-1087: - Thanks for addressing all the changes. I do recommend that this patch get committed. Updatable result sets

[jira] Commented: (DERBY-1087) Updatable result sets behave different depending on the type of query used to generate the result set

[ http://issues.apache.org/jira/browse/DERBY-1087?page=comments#action_12379061 ] Andreas Korneliussen commented on DERBY-1087: - I failed to notice that the test had been removed from jdbcapi, instead of derbynetclientmats Updatable result

[jira] Updated: (DERBY-1276) Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be populated

[ http://issues.apache.org/jira/browse/DERBY-1276?page=all ] Andreas Korneliussen updated DERBY-1276: Attachment: derbyall_report.txt Uloading result of derbyall. Test failed in OnlineBackup, do not see that it could be related to the patch

[jira] Commented: (DERBY-1276) Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be populated

[ http://issues.apache.org/jira/browse/DERBY-1276?page=comments#action_12379065 ] Andreas Korneliussen commented on DERBY-1276: - Meant Uploading, not Uloading in my previous comment. Calling ResultSet.isLast() on a scrollable insensitive

[jira] Commented: (DERBY-1087) Updatable result sets behave different depending on the type of query used to generate the result set

[ http://issues.apache.org/jira/browse/DERBY-1087?page=comments#action_12379084 ] Andreas Korneliussen commented on DERBY-1087: - Great, then I do not have any issues w.r.t this patch, and (again) recommend it being committed. Updatable result

[jira] Commented: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12378856 ] Andreas Korneliussen commented on DERBY-1251: - - //After a delete, the ResultSet will be positioned right before - //the next row. - rowData = null

[jira] Updated: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=all ] Andreas Korneliussen updated DERBY-1251: Attachment: DERBY-1251v3.diff Attached is a patch (DERBY-1251v3.diff) which addresses the review comments. The changes in deleteRow() behavior

[jira] Commented: (DERBY-1308) Tests jdbcapi/HoldabilityTest.junit, jdbcapi/UpdateXXXTest.junit,jdbcapi/SURTest.junit fail on wctme5.7_foundation

[ http://issues.apache.org/jira/browse/DERBY-1308?page=comments#action_12378852 ] Andreas Korneliussen commented on DERBY-1308: - I think this could be a regression, since as part of DERBY-993, Myrna was able to run the following tests

[jira] Reopened: (DERBY-1058) derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.

[ http://issues.apache.org/jira/browse/DERBY-1058?page=all ] Andreas Korneliussen reopened DERBY-1058: - Reopen to see if this could go to 10.1.3 branch. If this is taken to the 10.1.3 branch, I would suggest trying to take the first diff

[jira] Updated: (DERBY-1058) derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed.

[ http://issues.apache.org/jira/browse/DERBY-1058?page=all ] Andreas Korneliussen updated DERBY-1058: Fix Version: 10.1.3.0 derby fails supporting holdable scrollable resultset: ERROR XSCB8: The btree conglomerate 1,141,037,436,752 is closed

[jira] Updated: (DERBY-717) update doc on updatable cursors

[ http://issues.apache.org/jira/browse/DERBY-717?page=all ] Andreas Korneliussen updated DERBY-717: --- Attachment: DERBY-717v3.diff DERBY-717v3.stat derby-717v3.tar.gz The attached files (DERBY-717v3.*) now also

[jira] Commented: (DERBY-1276) Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be populated

[ http://issues.apache.org/jira/browse/DERBY-1276?page=comments#action_12378932 ] Andreas Korneliussen commented on DERBY-1276: - Yes, I ran derbyall with this change. Found that * derbyall/derbynetmats/derbynetmats.fail:stress/stress.multi

[jira] Commented: (DERBY-1087) Updatable result sets behave different depending on the type of query used to generate the result set

[ http://issues.apache.org/jira/browse/DERBY-1087?page=comments#action_12378595 ] Andreas Korneliussen commented on DERBY-1087: - I have downloaded the patch, and first only applied the test, to see that it failed before taking in the changes

[jira] Commented: (DERBY-1087) Updatable result sets behave different depending on the type of query used to generate the result set

[ http://issues.apache.org/jira/browse/DERBY-1087?page=comments#action_12378596 ] Andreas Korneliussen commented on DERBY-1087: - Review: The patch looks good, here are some minor comments: 1. In java/engine/org/apache/derby/impl/sql/compile

[jira] Updated: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=all ] Andreas Korneliussen updated DERBY-1251: Derby Info: [Patch Available] A patch (DERBY-1251v2.diff) is available for review. cancelRowUpdates() affects rows updated with updateRow

[jira] Updated: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=all ] Andreas Korneliussen updated DERBY-1251: Attachment: DERBY-1251v2.diff DERBY-1251v2.stat Embedded: In this patch (DERBY-1251v2.diff) I have addressed the problem

[jira] Updated: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=all ] Andreas Korneliussen updated DERBY-1251: Attachment: derbyall_report.txt Attaching report from derbyall, with patch DERBY-1251v2.diff cancelRowUpdates() affects rows updated

[jira] Updated: (DERBY-1276) Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be populated

[ http://issues.apache.org/jira/browse/DERBY-1276?page=all ] Andreas Korneliussen updated DERBY-1276: Attachment: DERBY-1276.diff DERBY-1276.stat A patch which fixes the problem by going to the next row (if necessary) instead

[jira] Updated: (DERBY-1276) Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be populated

[ http://issues.apache.org/jira/browse/DERBY-1276?page=all ] Andreas Korneliussen updated DERBY-1276: Version: 10.1.3.0 Derby Info: [Patch Available] Patch is available for review Calling ResultSet.isLast() on a scrollable insensitive

[jira] Commented: (DERBY-1234) Verify that we raise SQLException when calling methods on closed java.sql objects

[ http://issues.apache.org/jira/browse/DERBY-1234?page=comments#action_12377986 ] Andreas Korneliussen commented on DERBY-1234: - Yes, I am fine with the changes. Thanks for addressing this. Verify that we raise SQLException when calling

[jira] Updated: (DERBY-1277) Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row in scrollable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1277?page=all ] Andreas Korneliussen updated DERBY-1277: Summary: Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row in scrollable resultsets

[jira] Updated: (DERBY-1277) Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row in scrollable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1277?page=all ] Andreas Korneliussen updated DERBY-1277: Attachment: DERBY-1277.diff DERBY-1277.stat Attaching a fix, were ScrollInsensitiveResultSet do not return ExecRow from

[jira] Updated: (DERBY-1277) Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row in scrollable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1277?page=all ] Andreas Korneliussen updated DERBY-1277: Derby Info: [Patch Available] A patch is now available for review. Call to rs.isLast() may cause rs.getXXX() return values from the last row

[jira] Commented: (DERBY-1234) Verify that we raise SQLException when calling methods on closed java.sql objects

[ http://issues.apache.org/jira/browse/DERBY-1234?page=comments#action_12377780 ] Andreas Korneliussen commented on DERBY-1234: - I think maybe some of the added calls to checkIfClosed() are not necessary. I.e if you call rs.getInt(intcolumt

[jira] Created: (DERBY-1277) Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row in scrollable updatable resultsets

URL: http://issues.apache.org/jira/browse/DERBY-1277 Project: Derby Type: Bug Components: SQL Versions: 10.2.0.0 Reporter: Andreas Korneliussen Priority: Minor In scrollable updatable resultset, a call to rs.isLast() may cause rs.getXXX() return values

[jira] Assigned: (DERBY-1277) Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1277?page=all ] Andreas Korneliussen reassigned DERBY-1277: --- Assign To: Andreas Korneliussen Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row

[jira] Commented: (DERBY-846) Internationalze NetAgent to NetDatabaseMetadata40 in org.apache.derby.client.net

[ http://issues.apache.org/jira/browse/DERBY-846?page=comments#action_12377584 ] Andreas Korneliussen commented on DERBY-846: In my review comments posted on derbydev, I commented on the error message: ERROR 08004: Connection authorization

Re: [VOTE] Halley Pacheco de Oliveira as committer

[ ] +1 Yes, Halley should become a committer Andreas

Re: [VOTE] Halley Pacheco de Oliveira as committer

Andreas Korneliussen wrote: [ ] +1 Yes, Halley should become a committer Andreas Meant: [X] +1 Yes, Halley should become a committer Andreas

[jira] Created: (DERBY-1276) Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be popultated

/browse/DERBY-1276 Project: Derby Type: Improvement Components: SQL Versions: 10.2.0.0 Reporter: Andreas Korneliussen Assigned to: Andreas Korneliussen Priority: Minor The following is not a bug, however some applications do not always need to scroll to the last row

[jira] Updated: (DERBY-1276) Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be populated

[ http://issues.apache.org/jira/browse/DERBY-1276?page=all ] Andreas Korneliussen updated DERBY-1276: Summary: Calling ResultSet.isLast() on a scrollable insensitive resultset, causes the entire ResultSet to be populated (was: Calling

Re: DRDA folks: Please review DERBY-846 patch

David W. Van Couvering wrote: Hi, all. This patch is blocking further i18n work for me. I also don't want to have to do any merges and re-run derbyall. If you could get any comments in by noon, that would be appreciated, otherwise I will go ahead and check in and we can fix anything

[jira] Commented: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12377466 ] Andreas Korneliussen commented on DERBY-1251: - Withdrawing the patch DERBY-1251.diff. It turns out that the currentRow attribute in the EmbedResultSet may

[jira] Updated: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=all ] Andreas Korneliussen updated DERBY-1251: Derby Info: (was: [Patch Available]) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

Re: DRDA folks: Please review DERBY-846 patch

to check-in or not. Andreas Let me respond to your comments below. Andreas Korneliussen wrote: David W. Van Couvering wrote: Hi, all. This patch is blocking further i18n work for me. I also don't want to have to do any merges and re-run derbyall. If you could get any comments in by noon

[jira] Updated: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=all ] Andreas Korneliussen updated DERBY-1251: Attachment: DERBY-1251.diff DERBY-1251.stat derbyall_report.txt Changes to address this bug: Embedded JDBC

[jira] Updated: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=all ] Andreas Korneliussen updated DERBY-1251: Derby Info: [Patch Available] cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

Re: 10.2 release in August?

Knut Anders Hatlen wrote: Hi all, I was just about to send out a mail yesterday, proposing a 10.2 release in August, when I noticed that Kathey and Andrew had published the 10.1.3 release schedule on the wiki. Although there might be collisions between the two schedules, I will post my

Re: 10.2 release in August?

Jean T. Anderson wrote: Andreas Korneliussen wrote: ... +1 I would like to support this release, and the proposed schedule seems to be realisitic in terms of getting the SUR features (+related bugfixes) into the release. at the risk out sounding totally out of touch what's SUR

[jira] Created: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

Type: Bug Components: JDBC, Network Client Versions: 10.2.0.0 Reporter: Andreas Korneliussen Assigned to: Andreas Korneliussen Priority: Minor If an application does the following: rs.updateInt(1, newValueCol1); rs.updateRow(); rs.updateInt(2, newValueCol2

[jira] Commented: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12376218 ] Andreas Korneliussen commented on DERBY-1251: - The bug was detected while adding the following testcase in SURTest: /** * Test that you can correctly run

[jira] Commented: (DERBY-1251) cancelRowUpdates() affects rows updated with updateRow() in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1251?page=comments#action_12376245 ] Andreas Korneliussen commented on DERBY-1251: - Actually, the previous comment indicates another related bug: after updateRow(), rs.getXXX() returns the old value

[jira] Created: (DERBY-1249) cursor operation conflict incorrectly handled in scrollable updatable resultsets

Components: JDBC, Network Client Versions: 10.2.0.0 Reporter: Andreas Korneliussen Assigned to: Andreas Korneliussen Priority: Minor In a scroll insensitive updatable resultset: When using updateRow() or deleteRow() to update the current row, and the row has been deleted by another

Re: [jira] Commented: (DERBY-1141) test harness usage of useprocess needs improvement

When running junit.textui.TestRunner testClass (as a stand-alone process, useprocess=true) junit extracts the TestSuite (extending from Test) from the suite() method if there is such a method, and runs it. If there is no such method, the JUnit TestRunner (in junit.runner.getTest(...))

[jira] Updated: (DERBY-717) update doc on updatable cursors

[ http://issues.apache.org/jira/browse/DERBY-717?page=all ] Andreas Korneliussen updated DERBY-717: --- Description: The new features introduced in DERBY-690, DERBY-231, DERBY-775 and DERBY-100 should be documented in the Derby reference manual

[jira] Updated: (DERBY-717) update doc on updatable cursors

[ http://issues.apache.org/jira/browse/DERBY-717?page=all ] Andreas Korneliussen updated DERBY-717: --- Description: The new features introduced in DERBY-690, DERBY-231, DERBY-775 and DERBY-100 should be documented in the Derby developer guide

[jira] Updated: (DERBY-717) update doc on updatable cursors

[ http://issues.apache.org/jira/browse/DERBY-717?page=all ] Andreas Korneliussen updated DERBY-717: --- Attachment: DERBY-717.diff DERBY-717.stat derby-717.tar.gz The patch DERBY-717.diff has the following new topics

[jira] Updated: (DERBY-717) update doc on updatable cursors

[ http://issues.apache.org/jira/browse/DERBY-717?page=all ] Andreas Korneliussen updated DERBY-717: --- Derby Info: [Patch Available] update doc on updatable cursors --- Key: DERBY-717 URL: http

[jira] Updated: (DERBY-100) Add support for insert functionality using JDBC 2.0 updatable resultset apis

[ http://issues.apache.org/jira/browse/DERBY-100?page=all ] Andreas Korneliussen updated DERBY-100: --- Fix Version: 10.2.0.0 Derby Info: [Patch Available, Release Note Needed] Release note suggestion: Updatable resultsets now supports inserting

[jira] Commented: (DERBY-100) Add support for insert functionality using JDBC 2.0 updatable resultset apis

[ http://issues.apache.org/jira/browse/DERBY-100?page=comments#action_12375368 ] Andreas Korneliussen commented on DERBY-100: I think this issue can be closed, along with DERBY-99 and DERBY-98, since work has been done to support these features

[jira] Updated: (DERBY-690) Add scrollable, updatable, insensitive result sets

[ http://issues.apache.org/jira/browse/DERBY-690?page=all ] Andreas Korneliussen updated DERBY-690: --- Derby Info: [Patch Available, Release Note Needed] Add scrollable, updatable, insensitive result sets

<    1   2   3   4   5   6   >