[jira] Commented: (DERBY-2042) Provide documentation for new RENAME COLUMN statement

[ http://issues.apache.org/jira/browse/DERBY-2042?page=comments#action_12447499 ] Knut Anders Hatlen commented on DERBY-2042: --- Hi Bryan, I had a look at the HTML page. I haven't tested how RENAME COLUMN actually works, nor have I

[jira] Commented: (DERBY-2042) Provide documentation for new RENAME COLUMN statement

[ http://issues.apache.org/jira/browse/DERBY-2042?page=comments#action_12447503 ] Knut Anders Hatlen commented on DERBY-2042: --- In the example that shows how to change the type of a column, is it really necessary to rename c1 to

[jira] Closed: (DERBY-2046) Make class org.apache.derby.iapi.store.raw.PageKey final

[ http://issues.apache.org/jira/browse/DERBY-2046?page=all ] Knut Anders Hatlen closed DERBY-2046. - Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 471862. Make class

[jira] Updated: (DERBY-2023) Ensure all tests called by jdbc40._Suite run in embedded and client as required.

[ http://issues.apache.org/jira/browse/DERBY-2023?page=all ] Knut Anders Hatlen updated DERBY-2023: -- Fix Version/s: 10.3.0.0 Derby Info: (was: [Patch Available]) Thanks for reviewing, Dan! Committed revision 472016. I'm leaving the issue

[jira] Commented: (DERBY-2050) Manipulating CachedItems could be more efficient

[ http://issues.apache.org/jira/browse/DERBY-2050?page=comments#action_12447836 ] Knut Anders Hatlen commented on DERBY-2050: --- I don't think this should affect memory usage much since the JVM seems to allocate multiples of 8 bytes. I

[jira] Resolved: (DERBY-2023) Ensure all tests called by jdbc40._Suite run in embedded and client as required.

[ http://issues.apache.org/jira/browse/DERBY-2023?page=all ] Knut Anders Hatlen resolved DERBY-2023. --- Resolution: Fixed Number of tests in jdbc4._Suite increased from 2354 to 4133. All passed. Thanks Dan. Ensure all tests called by

[jira] Commented: (DERBY-2042) Provide documentation for new RENAME COLUMN statement

[ http://issues.apache.org/jira/browse/DERBY-2042?page=comments#action_12448072 ] Knut Anders Hatlen commented on DERBY-2042: --- Thanks Bryan, the changes look great! One last comment. I looked at how the page for CREATE INDEX defined

[jira] Commented: (DERBY-2050) Manipulating CachedItems could be more efficient

[ http://issues.apache.org/jira/browse/DERBY-2050?page=comments#action_12448155 ] Knut Anders Hatlen commented on DERBY-2050: --- I haven't tested the performance impact, but I definitely think the patch makes the code cleaner. A couple

[jira] Commented: (DERBY-2056) junitTests/derbyNet/CompatibilityTest.java fails with IBM JVM 142 and 15 on both Windows and Linux platforms

[ http://issues.apache.org/jira/browse/DERBY-2056?page=comments#action_12448264 ] Knut Anders Hatlen commented on DERBY-2056: --- It fails with Sun's JVM too. See

[jira] Commented: (DERBY-2047) TestDataSourceFactory doesn't work correctly outside the old harness

[ http://issues.apache.org/jira/browse/DERBY-2047?page=comments#action_12448383 ] Knut Anders Hatlen commented on DERBY-2047: --- It seems like the 472187 and/or 472228 commit broke a couple of tests in the old harness: * Diff

[jira] Resolved: (DERBY-2050) Manipulating CachedItems could be more efficient

[ http://issues.apache.org/jira/browse/DERBY-2050?page=all ] Knut Anders Hatlen resolved DERBY-2050. --- Resolution: Fixed Assignee: Dyre Tjeldvoll Thanks Dyre. Derbyall and the JUnit tests ran cleanly (except a couple of known issues).

[jira] Closed: (DERBY-2038) lang/releaseCompileLocks.sql and lang/closed.java fail under JDK 1.6 in insane mode

[ http://issues.apache.org/jira/browse/DERBY-2038?page=all ] Knut Anders Hatlen closed DERBY-2038. - Fix Version/s: 10.3.0.0 Resolution: Fixed Assignee: Knut Anders Hatlen Committed revision 472859. lang/releaseCompileLocks.sql and

[jira] Commented: (DERBY-2042) Provide documentation for new RENAME COLUMN statement

[ http://issues.apache.org/jira/browse/DERBY-2042?page=comments#action_12448474 ] Knut Anders Hatlen commented on DERBY-2042: --- Thanks Bryan, I think the latest version looks good. Provide documentation for new RENAME COLUMN statement

[jira] Created: (DERBY-2067) Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java

Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java - Key: DERBY-2067 URL: http://issues.apache.org/jira/browse/DERBY-2067 Project:

[jira] Commented: (DERBY-2067) Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java

[ http://issues.apache.org/jira/browse/DERBY-2067?page=comments#action_12448558 ] Knut Anders Hatlen commented on DERBY-2067: --- The assert failure is raised on a connection to a Derby instance which has been shut down. It is raised

[jira] Updated: (DERBY-2067) Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java

[ http://issues.apache.org/jira/browse/DERBY-2067?page=all ] Knut Anders Hatlen updated DERBY-2067: -- Attachment: derby-2067.diff I propose that we change the assert in EmbedConnection.restoreContextStack() as suggested in the attached patch

[jira] Updated: (DERBY-2067) Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java

[ http://issues.apache.org/jira/browse/DERBY-2067?page=all ] Knut Anders Hatlen updated DERBY-2067: -- Assignee: Knut Anders Hatlen Derby Info: [Patch Available] Assert failure in EmbedConnection.restoreContextStack() when running

[jira] Closed: (DERBY-2067) Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java

[ http://issues.apache.org/jira/browse/DERBY-2067?page=all ] Knut Anders Hatlen closed DERBY-2067. - Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 473687. Assert failure in

[jira] Resolved: (DERBY-2009) Modify links to reflect that Sun DBTG test reports have moved to dbtg.thresher.com

[ http://issues.apache.org/jira/browse/DERBY-2009?page=all ] Knut Anders Hatlen resolved DERBY-2009. --- Resolution: Fixed Derby Info: (was: [Patch Available]) Thank you, Ole. I applied your patch and rebuilt the website. Committed with

[jira] Assigned: (DERBY-1704) Allow more concurrency in the lock manager

[ http://issues.apache.org/jira/browse/DERBY-1704?page=all ] Knut Anders Hatlen reassigned DERBY-1704: - Assignee: Knut Anders Hatlen Allow more concurrency in the lock manager -- Key:

[jira] Commented: (DERBY-1704) Allow more concurrency in the lock manager

[ http://issues.apache.org/jira/browse/DERBY-1704?page=comments#action_12449309 ] Knut Anders Hatlen commented on DERBY-1704: --- I am planning to partition the hash table in LockSet along the lines of the split-hashtables.diff patch.

[jira] Updated: (DERBY-801) Allow parallel access to data files.

[ http://issues.apache.org/jira/browse/DERBY-801?page=all ] Knut Anders Hatlen updated DERBY-801: - Fix Version/s: 10.3.0.0 Derby Info: (was: [Patch Available]) Committed revision 474695. I don't think there is much left before the issue

[jira] Commented: (DERBY-1704) Allow more concurrency in the lock manager

[ http://issues.apache.org/jira/browse/DERBY-1704?page=comments#action_12449899 ] Knut Anders Hatlen commented on DERBY-1704: --- Thanks. Do you think it would be better to leave SinglePool as it is and create a new (perhaps optional)

[jira] Commented: (DERBY-1132) Truncation Error with Concat

[ http://issues.apache.org/jira/browse/DERBY-1132?page=comments#action_12450082 ] Knut Anders Hatlen commented on DERBY-1132: --- Here's another repro. It doesn't reproduce the the exception, but it could perhaps shed some more light on

[jira] Created: (DERBY-2089) jdbc4/VerifySignatures.junit is failing

jdbc4/VerifySignatures.junit is failing --- Key: DERBY-2089 URL: http://issues.apache.org/jira/browse/DERBY-2089 Project: Derby Issue Type: Bug Components: Regression Test Failure, Test

[jira] Updated: (DERBY-2089) jdbc4/VerifySignatures.junit is failing

[ http://issues.apache.org/jira/browse/DERBY-2089?page=all ] Knut Anders Hatlen updated DERBY-2089: -- Attachment: derby-2089.diff Adding connection attribute create=true made the test run successfully. jdbc4/VerifySignatures.junit is failing

[jira] Closed: (DERBY-2089) jdbc4/VerifySignatures.junit is failing

[ http://issues.apache.org/jira/browse/DERBY-2089?page=all ] Knut Anders Hatlen closed DERBY-2089. - Fix Version/s: 10.3.0.0 Resolution: Fixed Committed revision 475370. jdbc4/VerifySignatures.junit is failing

[jira] Created: (DERBY-2091) Increase coverage for StatementEventsTest

Increase coverage for StatementEventsTest - Key: DERBY-2091 URL: http://issues.apache.org/jira/browse/DERBY-2091 Project: Derby Issue Type: Improvement Components: JDBC, Test Affects

[jira] Resolved: (DERBY-2090) Broken link in Reference manual

[ http://issues.apache.org/jira/browse/DERBY-2090?page=all ] Knut Anders Hatlen resolved DERBY-2090. --- Fix Version/s: 10.2.1.8 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks, Kim and Olav!

[jira] Created: (DERBY-2099) Make BasePage.getPageId() final

Make BasePage.getPageId() final --- Key: DERBY-2099 URL: http://issues.apache.org/jira/browse/DERBY-2099 Project: Derby Issue Type: Improvement Components: Performance, Store Affects Versions:

[jira] Updated: (DERBY-2099) Make BasePage.getPageId() final

[ http://issues.apache.org/jira/browse/DERBY-2099?page=all ] Knut Anders Hatlen updated DERBY-2099: -- Attachment: getpageid.diff Make BasePage.getPageId() final --- Key: DERBY-2099

[jira] Closed: (DERBY-2099) Make BasePage.getPageId() final

[ http://issues.apache.org/jira/browse/DERBY-2099?page=all ] Knut Anders Hatlen closed DERBY-2099. - Fix Version/s: 10.3.0.0 Resolution: Fixed Committed revision 476662. Make BasePage.getPageId() final ---

[jira] Resolved: (DERBY-2102) JDBC.assertFullResultSet should handle byte arrays

[ http://issues.apache.org/jira/browse/DERBY-2102?page=all ] Knut Anders Hatlen resolved DERBY-2102. --- Resolution: Fixed Derby Info: (was: [Patch Available]) Thank you, Øystein! Committed revision 477645. JDBC.assertFullResultSet should

[jira] Created: (DERBY-2107) Move page latching out of the lock manager

Move page latching out of the lock manager -- Key: DERBY-2107 URL: http://issues.apache.org/jira/browse/DERBY-2107 Project: Derby Issue Type: Improvement Components: Services, Store

[jira] Closed: (DERBY-2038) lang/releaseCompileLocks.sql and lang/closed.java fail under JDK 1.6 in insane mode

[ http://issues.apache.org/jira/browse/DERBY-2038?page=all ] Knut Anders Hatlen closed DERBY-2038. - Fix Version/s: 10.2.1.8 Resolution: Fixed Committed to 10.2 with revision 478118. lang/releaseCompileLocks.sql and lang/closed.java fail

[jira] Commented: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.

[ http://issues.apache.org/jira/browse/DERBY-1434?page=comments#action_12452082 ] Knut Anders Hatlen commented on DERBY-1434: --- Hi Julo, I haven't followed the discussion about this bug closely enough to say whether the fix is correct,

[jira] Commented: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.

[ http://issues.apache.org/jira/browse/DERBY-1434?page=comments#action_12452247 ] Knut Anders Hatlen commented on DERBY-1434: --- Thanks for the explanations, Julo. They all make sense. So DRDAConnThread is supposed to check that the

[jira] Updated: (DERBY-2107) Move page latching out of the lock manager

[ http://issues.apache.org/jira/browse/DERBY-2107?page=all ] Knut Anders Hatlen updated DERBY-2107: -- Attachment: derby-2107-1a.diff derby-2107-1a.stat Here's a first patch (derby-2107-1a.diff) which implements latching locally in

[jira] Updated: (DERBY-2107) Move page latching out of the lock manager

[ http://issues.apache.org/jira/browse/DERBY-2107?page=all ] Knut Anders Hatlen updated DERBY-2107: -- Component/s: Performance Derby Info: [Patch Available] Move page latching out of the lock manager --

[jira] Resolved: (DERBY-812) Scripts to publish Derby test results

[ http://issues.apache.org/jira/browse/DERBY-812?page=all ] Knut Anders Hatlen resolved DERBY-812. -- Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Thank you for contributing the scripts, Ole!

[jira] Resolved: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.

[ http://issues.apache.org/jira/browse/DERBY-1434?page=all ] Knut Anders Hatlen resolved DERBY-1434. --- Resolution: Fixed Derby Info: (was: [Patch Available]) Thank you. I ran derbyall and the JUnit tests with no failures. Committed revision

[jira] Created: (DERBY-2115) Some master files don't have the svn:eol-style property

Some master files don't have the svn:eol-style property --- Key: DERBY-2115 URL: http://issues.apache.org/jira/browse/DERBY-2115 Project: Derby Issue Type: Bug Components: Test

[jira] Closed: (DERBY-2115) Some master files don't have the svn:eol-style property

[ http://issues.apache.org/jira/browse/DERBY-2115?page=all ] Knut Anders Hatlen closed DERBY-2115. - Fix Version/s: 10.3.0.0 Resolution: Fixed Fixed with this command: for i in `find java/testing/org/apache/derbyTesting/ -name *.out`; do

[jira] Created: (DERBY-2116) Test files missing svn:eol-style

Test files missing svn:eol-style Key: DERBY-2116 URL: http://issues.apache.org/jira/browse/DERBY-2116 Project: Derby Issue Type: Bug Components: Test Affects Versions: 10.3.0.0

[jira] Closed: (DERBY-2116) Test files missing svn:eol-style

[ http://issues.apache.org/jira/browse/DERBY-2116?page=all ] Knut Anders Hatlen closed DERBY-2116. - Fix Version/s: 10.3.0.0 Resolution: Fixed for i in `find java/testing -name *.sql -o -name *.java`; do svn proplist $i | grep

[jira] Updated: (DERBY-812) Scripts to publish Derby test results

[ http://issues.apache.org/jira/browse/DERBY-812?page=all ] Knut Anders Hatlen updated DERBY-812: - Attachment: 812-headers.diff I guess the scripts should have had licence headers. The attached patch adds headers to all the scripts and html files.

[jira] Commented: (DERBY-812) Scripts to publish Derby test results

[ http://issues.apache.org/jira/browse/DERBY-812?page=comments#action_12452575 ] Knut Anders Hatlen commented on DERBY-812: -- Committed 812-headers.diff with revision 479119. Scripts to publish Derby test results

[jira] Created: (DERBY-2117) Intermittent failure in lang/compressTable.sql

Intermittent failure in lang/compressTable.sql -- Key: DERBY-2117 URL: http://issues.apache.org/jira/browse/DERBY-2117 Project: Derby Issue Type: Bug Components: Regression Test Failure

[jira] Commented: (DERBY-2110) message typos: error 42X52, XJ100.S, XBCXU/XBCXV...

[ http://issues.apache.org/jira/browse/DERBY-2110?page=comments#action_12453522 ] Knut Anders Hatlen commented on DERBY-2110: --- I think the message means that there is a mix of LF and CR-LF in the file. You could try to run a dos2unix

[jira] Commented: (DERBY-2025) convert lang/updatableResultSet.java to Junit

[ http://issues.apache.org/jira/browse/DERBY-2025?page=comments#action_12453601 ] Knut Anders Hatlen commented on DERBY-2025: --- The patch looks good. Some small comments: - I believe testResultSetPositionedBeforeNextAfterDeleteRow() is

[jira] Commented: (DERBY-2119) derby.drda.timeSlice property is incorrectly documented in admin guide as derby.drda.timeslice

[ http://issues.apache.org/jira/browse/DERBY-2119?page=comments#action_12453711 ] Knut Anders Hatlen commented on DERBY-2119: --- Thanks for fixing this so quickly, Kim! Committed revision 479770. Should we also fix this in the Brazilian

[jira] Updated: (DERBY-2119) derby.drda.timeSlice property is incorrectly documented in admin guide as derby.drda.timeslice

[ http://issues.apache.org/jira/browse/DERBY-2119?page=all ] Knut Anders Hatlen updated DERBY-2119: -- Attachment: DERBY-2119-pt_BR.diff Attaching patch which fixes the pt_BR version. derby.drda.timeSlice property is incorrectly documented in admin

[jira] Resolved: (DERBY-2119) derby.drda.timeSlice property is incorrectly documented in admin guide as derby.drda.timeslice

[ http://issues.apache.org/jira/browse/DERBY-2119?page=all ] Knut Anders Hatlen resolved DERBY-2119. --- Fix Version/s: 10.2.2.0 10.3.0.0 Resolution: Fixed Committed fix of the Brazilian manual with revision 479775. Merged

[jira] Commented: (DERBY-2110) message typos: error 42X52, XJ100.S, XBCXU/XBCXV...

[ http://issues.apache.org/jira/browse/DERBY-2110?page=comments#action_12453898 ] Knut Anders Hatlen commented on DERBY-2110: --- The changes look good. +1 to commit. message typos: error 42X52, XJ100.S, XBCXU/XBCXV...

[jira] Commented: (DERBY-2108) Implement SSL/TLS communication between client and server

[ http://issues.apache.org/jira/browse/DERBY-2108?page=comments#action_12453905 ] Knut Anders Hatlen commented on DERBY-2108: --- Thank you for contributing this patch, Bernt! I think it is a great improvement. As you said, there is room

[jira] Created: (DERBY-2122) Optimize ContainerLock.isCompatible()

Optimize ContainerLock.isCompatible() - Key: DERBY-2122 URL: http://issues.apache.org/jira/browse/DERBY-2122 Project: Derby Issue Type: Improvement Components: Store Affects Versions:

[jira] Updated: (DERBY-2122) Optimize ContainerLock.isCompatible()

[ http://issues.apache.org/jira/browse/DERBY-2122?page=all ] Knut Anders Hatlen updated DERBY-2122: -- Component/s: Performance Optimize ContainerLock.isCompatible() - Key: DERBY-2122

[jira] Updated: (DERBY-2122) Optimize ContainerLock.isCompatible()

[ http://issues.apache.org/jira/browse/DERBY-2122?page=all ] Knut Anders Hatlen updated DERBY-2122: -- Attachment: derby-2122-v1.diff derby-2122-v1.stat The attached patch removes the compatibility matrix from ContainerLock and

[jira] Updated: (DERBY-2122) Optimize ContainerLock.isCompatible()

[ http://issues.apache.org/jira/browse/DERBY-2122?page=all ] Knut Anders Hatlen updated DERBY-2122: -- Derby Info: [Patch Available] Optimize ContainerLock.isCompatible() - Key: DERBY-2122

[jira] Commented: (DERBY-2122) Optimize ContainerLock.isCompatible()

[ http://issues.apache.org/jira/browse/DERBY-2122?page=comments#action_12454087 ] Knut Anders Hatlen commented on DERBY-2122: --- Oh, I forgot... Derbyall and the JUnit tests ran cleanly. Optimize ContainerLock.isCompatible()

[jira] Created: (DERBY-2123) Remove workaround for old JIT bug from StoredPage

Remove workaround for old JIT bug from StoredPage - Key: DERBY-2123 URL: http://issues.apache.org/jira/browse/DERBY-2123 Project: Derby Issue Type: Improvement Components: Store

[jira] Commented: (DERBY-2122) Optimize ContainerLock.isCompatible()

[ http://issues.apache.org/jira/browse/DERBY-2122?page=comments#action_12454117 ] Knut Anders Hatlen commented on DERBY-2122: --- Thanks Mike, that's a good point. Perhaps it would be even better if we left the 2-d arrays and built the

[jira] Updated: (DERBY-2123) Remove workaround for old JIT bug from StoredPage

[ http://issues.apache.org/jira/browse/DERBY-2123?page=all ] Knut Anders Hatlen updated DERBY-2123: -- Attachment: derby-2123-v1.diff derby-2123-v1.stat The attached patch makes inUserCode a local variable instead of a parameter for

[jira] Updated: (DERBY-2123) Remove workaround for old JIT bug from StoredPage

[ http://issues.apache.org/jira/browse/DERBY-2123?page=all ] Knut Anders Hatlen updated DERBY-2123: -- Derby Info: [Patch Available] Remove workaround for old JIT bug from StoredPage -

[jira] Updated: (DERBY-2122) Optimize ContainerLock.isCompatible()

[ http://issues.apache.org/jira/browse/DERBY-2122?page=all ] Knut Anders Hatlen updated DERBY-2122: -- Attachment: derby-2122-v2.diff derby-2122-v2.stat New and simpler patch attached (v2). This patch keeps the compatibility arrays

[jira] Closed: (DERBY-2123) Remove workaround for old JIT bug from StoredPage

[ http://issues.apache.org/jira/browse/DERBY-2123?page=all ] Knut Anders Hatlen closed DERBY-2123. - Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 480861. Remove workaround for old

[jira] Closed: (DERBY-2122) Optimize ContainerLock.isCompatible()

[ http://issues.apache.org/jira/browse/DERBY-2122?page=all ] Knut Anders Hatlen closed DERBY-2122. - Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed v2 patch with revision 481181. Optimize

[jira] Created: (DERBY-2140) BlobClob4BlobTest.testSelfDestructiveClob() fails with ERROR X0X95: Operation 'DROP TABLE' cannot be performed on object 'TESTCLOB' because there is an open ResultSet dep

BlobClob4BlobTest.testSelfDestructiveClob() fails with ERROR X0X95: Operation 'DROP TABLE' cannot be performed on object 'TESTCLOB' because there is an open ResultSet dependent on that object.

[jira] Updated: (DERBY-2140) BlobClob4BlobTest.testSelfDestructiveClob() fails with ERROR X0X95: Operation 'DROP TABLE' cannot be performed on object 'TESTCLOB' because there is an open ResultSet dep

[ http://issues.apache.org/jira/browse/DERBY-2140?page=all ] Knut Anders Hatlen updated DERBY-2140: -- Attachment: derby-2140.diff The attached patch makes testSelfDestructiveClob() close its result set and statement.

[jira] Closed: (DERBY-2140) BlobClob4BlobTest.testSelfDestructiveClob() fails with ERROR X0X95: Operation 'DROP TABLE' cannot be performed on object 'TESTCLOB' because there is an open ResultSet depe

[ http://issues.apache.org/jira/browse/DERBY-2140?page=all ] Knut Anders Hatlen closed DERBY-2140. - Fix Version/s: 10.3.0.0 Resolution: Fixed Committed revision 482129. BlobClob4BlobTest.testSelfDestructiveClob() fails with ERROR X0X95:

[jira] Commented: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement

[ http://issues.apache.org/jira/browse/DERBY-1231?page=comments#action_1246 ] Knut Anders Hatlen commented on DERBY-1231: --- The patch looks correct to me. Some minor comments: In lessThanString() the following is changed: -

[jira] Commented: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement

[ http://issues.apache.org/jira/browse/DERBY-1231?page=comments#action_12455563 ] Knut Anders Hatlen commented on DERBY-1231: --- Dyre wrote: I'll let you figure out if it is safe to change metadata.properties now, or if that could

[jira] Created: (DERBY-2149) Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction

Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction - Key: DERBY-2149 URL: http://issues.apache.org/jira/browse/DERBY-2149 Project: Derby

[jira] Created: (DERBY-2150) Reduce use of synchronized collections in GenericLanguageConnectionContext

Reduce use of synchronized collections in GenericLanguageConnectionContext -- Key: DERBY-2150 URL: http://issues.apache.org/jira/browse/DERBY-2150 Project: Derby Issue

[jira] Created: (DERBY-2155) checkDataSource and checkDataSource30 fail in the tinderbox test

checkDataSource and checkDataSource30 fail in the tinderbox test Key: DERBY-2155 URL: http://issues.apache.org/jira/browse/DERBY-2155 Project: Derby Issue Type: Bug

[jira] Assigned: (DERBY-2155) checkDataSource and checkDataSource30 fail in the tinderbox test

[ http://issues.apache.org/jira/browse/DERBY-2155?page=all ] Knut Anders Hatlen reassigned DERBY-2155: - Assignee: Knut Anders Hatlen checkDataSource and checkDataSource30 fail in the tinderbox test

[jira] Updated: (DERBY-2155) checkDataSource and checkDataSource30 fail in the tinderbox test

[ http://issues.apache.org/jira/browse/DERBY-2155?page=all ] Knut Anders Hatlen updated DERBY-2155: -- Attachment: derby-2155.diff derby-2155.stat The attached patch updates the master files so that the tests run cleanly. It also

[jira] Resolved: (DERBY-2155) checkDataSource and checkDataSource30 fail in the tinderbox test

[ http://issues.apache.org/jira/browse/DERBY-2155?page=all ] Knut Anders Hatlen resolved DERBY-2155. --- Fix Version/s: 10.3.0.0 Resolution: Fixed Committed revision 482972. checkDataSource and checkDataSource30 fail in the tinderbox test

[jira] Commented: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.

[ http://issues.apache.org/jira/browse/DERBY-1434?page=comments#action_12455931 ] Knut Anders Hatlen commented on DERBY-1434: --- This fix cannot be merged to 10.2 automatically because it depends on some changes to the JUnit framework

[jira] Commented: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement

[ http://issues.apache.org/jira/browse/DERBY-1231?page=comments#action_12455934 ] Knut Anders Hatlen commented on DERBY-1231: --- Looks good, +1 to commit. You could also remove NOTE: This may be null if the pattern is an empty string.

[jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0

[ http://issues.apache.org/jira/browse/DERBY-1471?page=comments#action_12456093 ] Knut Anders Hatlen commented on DERBY-1471: --- I have looked at patch 3. I don't know enough about layer B streaming to say whether all details of the

[jira] Closed: (DERBY-2155) checkDataSource and checkDataSource30 fail in the tinderbox test

[ http://issues.apache.org/jira/browse/DERBY-2155?page=all ] Knut Anders Hatlen closed DERBY-2155. - Tinderbox hasn't failed since the fix was committed. Closing the issue. checkDataSource and checkDataSource30 fail in the tinderbox test

[jira] Updated: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

[ http://issues.apache.org/jira/browse/DERBY-1165?page=all ] Knut Anders Hatlen updated DERBY-1165: -- Affects Version/s: 10.2.1.6 A test checking the transaction ids returned by xa_recover is needed

[jira] Commented: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

[ http://issues.apache.org/jira/browse/DERBY-1165?page=comments#action_12456740 ] Knut Anders Hatlen commented on DERBY-1165: --- Since this is already tested in jdk1.3, and jdk 1.3 will not be supported in 10.3, I suggest that we close

[jira] Commented: (DERBY-2107) Move page latching out of the lock manager

[ http://issues.apache.org/jira/browse/DERBY-2107?page=comments#action_12456770 ] Knut Anders Hatlen commented on DERBY-2107: --- The first may have been an existing issue: 1) The field nestedLatch is used under synchronization when

[jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0

[ http://issues.apache.org/jira/browse/DERBY-1471?page=comments#action_12458092 ] Knut Anders Hatlen commented on DERBY-1471: --- I have tested the lengthless versions of PreparedStatement.setClob(),

[jira] Resolved: (DERBY-2060) SET CURRENT ISOLATION in ref.man refers java.sql.Connection.setTransactionLevel instead of java.sql.Connection.setTransactionIsolation

[ http://issues.apache.org/jira/browse/DERBY-2060?page=all ] Knut Anders Hatlen resolved DERBY-2060. --- Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 487088. SET CURRENT ISOLATION

[jira] Closed: (DERBY-1165) A test checking the transaction ids returned by xa_recover is needed

[ http://issues.apache.org/jira/browse/DERBY-1165?page=all ] Knut Anders Hatlen closed DERBY-1165. - Resolution: Won't Fix A test checking the transaction ids returned by xa_recover is needed

[jira] Updated: (DERBY-2107) Move page latching out of the lock manager

[ http://issues.apache.org/jira/browse/DERBY-2107?page=all ] Knut Anders Hatlen updated DERBY-2107: -- Attachment: derby-2107-1b.diff Attaching a new version of the patch to address Dan's comments. (Improved synchronization and comments.) If this

[jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0

[ http://issues.apache.org/jira/browse/DERBY-1471?page=comments#action_12458486 ] Knut Anders Hatlen commented on DERBY-1471: --- Thank you, Tomohito! The changes look good to me. I have verified that the latest patch works with a new

[jira] Commented: (DERBY-2176) OutOfMemoryError in Network Server after running DOTS-like test for weeks

[ http://issues.apache.org/jira/browse/DERBY-2176?page=comments#action_12458519 ] Knut Anders Hatlen commented on DERBY-2176: --- I'm just guessing here, but the histogram of objects seems similar to what I would expect from DERBY-912,

[jira] Commented: (DERBY-2107) Move page latching out of the lock manager

[ http://issues.apache.org/jira/browse/DERBY-2107?page=comments#action_12458736 ] Knut Anders Hatlen commented on DERBY-2107: --- Thanks for your comments, Dan and Mike. It seems to me that all your comments are about the variants of

[jira] Updated: (DERBY-2149) Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction

[ http://issues.apache.org/jira/browse/DERBY-2149?page=all ] Knut Anders Hatlen updated DERBY-2149: -- Attachment: derby-2149-1a.diff The attached patch replaces four Vectors and one Hashtable in RAMTransaction with ArrayLists and a HashMap.

[jira] Assigned: (DERBY-2149) Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction

[ http://issues.apache.org/jira/browse/DERBY-2149?page=all ] Knut Anders Hatlen reassigned DERBY-2149: - Assignee: Knut Anders Hatlen Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction

[jira] Updated: (DERBY-2149) Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction

[ http://issues.apache.org/jira/browse/DERBY-2149?page=all ] Knut Anders Hatlen updated DERBY-2149: -- Derby Info: [Patch Available] Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction

[jira] Updated: (DERBY-2150) Reduce use of synchronized collections in GenericLanguageConnectionContext

[ http://issues.apache.org/jira/browse/DERBY-2150?page=all ] Knut Anders Hatlen updated DERBY-2150: -- Attachment: derby-2150-1a.diff I've had a partial patch for this issue in my sandbox for a while. Attaching it here so that it won't be lost. The

[jira] Updated: (DERBY-2149) Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction

[ http://issues.apache.org/jira/browse/DERBY-2149?page=all ] Knut Anders Hatlen updated DERBY-2149: -- Derby Info: (was: [Patch Available]) I reran the JUnit tests and got two failures in the nist suite. They seem related to the patch, so I'm

[jira] Updated: (DERBY-2149) Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction

[ http://issues.apache.org/jira/browse/DERBY-2149?page=all ] Knut Anders Hatlen updated DERBY-2149: -- Attachment: derby-2149-1b.diff Uploading a new patch. The problem with the previous one was a mix-up of two variable names. Have run derbyall and

[jira] Updated: (DERBY-2149) Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction

[ http://issues.apache.org/jira/browse/DERBY-2149?page=all ] Knut Anders Hatlen updated DERBY-2149: -- Derby Info: [Patch Available] Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction

[jira] Commented: (DERBY-2181) StandardException.printStackTrace() does not print the nested exception (cause)

[ http://issues.apache.org/jira/browse/DERBY-2181?page=comments#action_12458963 ] Knut Anders Hatlen commented on DERBY-2181: --- I don't believe this is true for SQLException.getNextException(). SQLException maintains separate chains

<    6   7   8   9   10   11   12   13   14   15   >