[jira] Assigned: (DERBY-1585) derbylang/procedureInTrigger: not able to create trigger due to an open ResultSet

[ http://issues.apache.org/jira/browse/DERBY-1585?page=all ] Deepa Remesh reassigned DERBY-1585: --- Assignee: (was: Deepa Remesh) After the initial analysis, I hadn't spent much time on this bug. Thanks for bringing this up. I'm unassigning now if

[jira] Commented: (DERBY-2084) getTransactionIsolation() in network client should not activate a transaction

[ http://issues.apache.org/jira/browse/DERBY-2084?page=comments#action_12449717 ] Deepa Remesh commented on DERBY-2084: - Bernt, I verified that your patch fixes the problem reported. I hadn't realized that the fix for DERBY-1148 would lead

[jira] Updated: (DERBY-638) setTransactionIsolation behaviour in network client driver is different from that of embedded driver

[ http://issues.apache.org/jira/browse/DERBY-638?page=all ] Deepa Remesh updated DERBY-638: --- Attachment: d638_repro2.java Thanks Bernt for looking at this issue. Patch1 seems better to me and will match more with the embedded implementation. With

[jira] Commented: (DERBY-638) setTransactionIsolation behaviour in network client driver is different from that of embedded driver

[ http://issues.apache.org/jira/browse/DERBY-638?page=comments#action_12448320 ] Deepa Remesh commented on DERBY-638: I now see the current implementation will commit the transaction in all cases. The exception was indeed misleading and

[jira] Commented: (DERBY-1897) junit test jdbcapi/_Suite fails with wctme5.7_foundation (j9 -jcl:foun) with NoClassDefFoundError: javax.sql.PooledConnection

[ http://issues.apache.org/jira/browse/DERBY-1897?page=comments#action_12442995 ] Deepa Remesh commented on DERBY-1897: - I too don't see this class in the jdbc.jar for wctme5.7/foundation. JSR169 is a subset of JDBC3.0.

[jira] Commented: (DERBY-1689) Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3

[ http://issues.apache.org/jira/browse/DERBY-1689?page=comments#action_12442394 ] Deepa Remesh commented on DERBY-1689: - Thanks Bryan for bringing this up. I see Yip has already submitted a patch for DERBY-630 with upgrade test for 10.1 to

[jira] Commented: (DERBY-1849) Tests lang/grantRevokeDDL.sql and lang/grantRevokeDDL2.sql fails on IBM WCTME 5.7 Foundation (jdkJ2ME Foundation Specification v1.0)

[ http://issues.apache.org/jira/browse/DERBY-1849?page=comments#action_12439320 ] Deepa Remesh commented on DERBY-1849: - Myrna said create Trigger fails with foundation because something in the Derby source code accessed in this statement

[jira] Closed: (DERBY-1326) Network server may abandon sessions when Derby system is shutdown and this causes intermittent hangs in the client

[ http://issues.apache.org/jira/browse/DERBY-1326?page=all ] Deepa Remesh closed DERBY-1326. --- Closing the issue as the fix is available in 10.2 and trunk. Thanks to Knut, Bryan (and others involved) in resolving this issue. Network server may abandon

[jira] Commented: (DERBY-1585) derbylang/procedureInTrigger: not able to create trigger due to an open ResultSet

[ http://issues.apache.org/jira/browse/DERBY-1585?page=comments#action_12437653 ] Deepa Remesh commented on DERBY-1585: - I had earlier said: In the code, the result set returned from executing the trigger action statement is closed.

[jira] Resolved: (DERBY-1826) Add JUnit utility methods for database/server shutdown

[ http://issues.apache.org/jira/browse/DERBY-1826?page=all ] Deepa Remesh resolved DERBY-1826. - Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Verified the patch has been committed to trunk and 10.2

[jira] Closed: (DERBY-1826) Add JUnit utility methods for database/server shutdown

[ http://issues.apache.org/jira/browse/DERBY-1826?page=all ] Deepa Remesh closed DERBY-1826. --- Add JUnit utility methods for database/server shutdown -- Key: DERBY-1826

[jira] Commented: (DERBY-1326) Network server may abandon sessions when Derby system is shutdown and this causes intermittent hangs in the client

[ http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434998 ] Deepa Remesh commented on DERBY-1326: - I'll file a separate issue for removing all the existing sessions after a restart. From Knut's comments, this is only

[jira] Created: (DERBY-1855) Clean up old sessions in network server after Derby engine is shutdown

Clean up old sessions in network server after Derby engine is shutdown -- Key: DERBY-1855 URL: http://issues.apache.org/jira/browse/DERBY-1855 Project: Derby Issue Type:

[jira] Updated: (DERBY-1844) jdbcapi/blobclob4BLOB.java fails with JCC drivers

[ http://issues.apache.org/jira/browse/DERBY-1844?page=all ] Deepa Remesh updated DERBY-1844: Environment: IBM JDK 1.4.2 Failure seen on IBM JDK 1.4.2. jdbcapi/blobclob4BLOB.java fails with JCC drivers

[jira] Updated: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ] Deepa Remesh updated DERBY-1522: Fix Version/s: 10.3.0.0 Derby Info: (was: [Patch Available]) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization

[jira] Assigned: (DERBY-1827) DatabasePropertyTestSetup.tearDown method gives exception when resetting properties

[ http://issues.apache.org/jira/browse/DERBY-1827?page=all ] Deepa Remesh reassigned DERBY-1827: --- Assignee: Deepa Remesh DatabasePropertyTestSetup.tearDown method gives exception when resetting properties

[jira] Closed: (DERBY-1827) DatabasePropertyTestSetup.tearDown method gives exception when resetting properties

[ http://issues.apache.org/jira/browse/DERBY-1827?page=all ] Deepa Remesh closed DERBY-1827. --- Fix Version/s: 10.2.1.0 10.3.0.0 Resolution: Fixed This was fixed as part of DERBY-1522. DatabasePropertyTestSetup.tearDown method

[jira] Resolved: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ] Deepa Remesh resolved DERBY-1522. - Resolution: Fixed Verified the fix for this issue is in trunk and 10.2. Thanks Mike and Rick for the commits. Switch(if supported) from Derby

[jira] Reopened: (DERBY-1103) Change the client driver to allow statements to be garbage-collected once they are not referenced in an application

[ http://issues.apache.org/jira/browse/DERBY-1103?page=all ] Deepa Remesh reopened DERBY-1103: - Reopening to uncheck the release notes needed box. This was included in the 10.1.3 release notes. Change the client driver to allow statements to

[jira] Updated: (DERBY-1103) Change the client driver to allow statements to be garbage-collected once they are not referenced in an application

[ http://issues.apache.org/jira/browse/DERBY-1103?page=all ] Deepa Remesh updated DERBY-1103: Derby Info: (was: [Release Note Needed]) Change the client driver to allow statements to be garbage-collected once they are not referenced in an

[jira] Closed: (DERBY-1103) Change the client driver to allow statements to be garbage-collected once they are not referenced in an application

[ http://issues.apache.org/jira/browse/DERBY-1103?page=all ] Deepa Remesh closed DERBY-1103. --- Resolution: Fixed Change the client driver to allow statements to be garbage-collected once they are not referenced in an application

[jira] Commented: (DERBY-1326) Network server may abandon sessions when Derby system is shutdown and this causes intermittent hangs in the client

[ http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434851 ] Deepa Remesh commented on DERBY-1326: - Thanks Knut for the answers. I still cannot wrap my head around old sessions hanging around in the server. I think this

[jira] Created: (DERBY-1845) OutOfMemoryError when running All suite directly using JUnit

OutOfMemoryError when running All suite directly using JUnit -- Key: DERBY-1845 URL: http://issues.apache.org/jira/browse/DERBY-1845 Project: Derby Issue Type: Test

[jira] Updated: (DERBY-1826) Add JUnit utility methods for database/server shutdown

[ http://issues.apache.org/jira/browse/DERBY-1826?page=all ] Deepa Remesh updated DERBY-1826: Derby Info: [Patch Available] derbyall ran okay using Sun jdk 1.4.2 on Windows XP. Few tests had failed due to some issues on my machine but on re-run, they

[jira] Commented: (DERBY-1326) Network server may abandon sessions when Derby system is shutdown and this causes intermittent hangs in the client

[ http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434547 ] Deepa Remesh commented on DERBY-1326: - Thanks Knut for working on this. Some questions/thoughts: * I think it is okay to re-use free/idle threads without

[jira] Commented: (DERBY-1585) derbylang/procedureInTrigger: not able to create trigger due to an open ResultSet

[ http://issues.apache.org/jira/browse/DERBY-1585?page=comments#action_12434571 ] Deepa Remesh commented on DERBY-1585: - Pasting the link to my previous comment to derby-dev for reference.

[jira] Assigned: (DERBY-1826) Add JUnit utility methods for database/server shutdown

[ http://issues.apache.org/jira/browse/DERBY-1826?page=all ] Deepa Remesh reassigned DERBY-1826: --- Assignee: Deepa Remesh Add JUnit utility methods for database/server shutdown --

[jira] Updated: (DERBY-1826) Add JUnit utility methods for database/server shutdown

[ http://issues.apache.org/jira/browse/DERBY-1826?page=all ] Deepa Remesh updated DERBY-1826: Attachment: derby-1826-v1.diff derby-1826-v1.status The attached patch 'derby-1826-v1.diff' adds methods to get connection by specifying

[jira] Created: (DERBY-1844) jdbcapi/blobclob4BLOB.java fails with JCC drivers

jdbcapi/blobclob4BLOB.java fails with JCC drivers - Key: DERBY-1844 URL: http://issues.apache.org/jira/browse/DERBY-1844 Project: Derby Issue Type: Test Components: Regression Test

[jira] Commented: (DERBY-1729) Invoking Java stored procedure that contains GRANT or REVOKE statement with CONTAINS SQL should fail.

[ http://issues.apache.org/jira/browse/DERBY-1729?page=comments#action_12433940 ] Deepa Remesh commented on DERBY-1729: - This is an issue with exception handling in jdk16. Reported as DERBY-1629. To temporarily resolve the regression test

[jira] Created: (DERBY-1841) lang/groupBy.sql fails with IBM j9 vms

lang/groupBy.sql fails with IBM j9 vms --- Key: DERBY-1841 URL: http://issues.apache.org/jira/browse/DERBY-1841 Project: Derby Issue Type: Test Components: Regression Test Failure

[jira] Commented: (DERBY-1785) junit tests fail with permission access problems when run with j9 jvms

[ http://issues.apache.org/jira/browse/DERBY-1785?page=comments#action_12434006 ] Deepa Remesh commented on DERBY-1785: - One more test fails with java.security.AccessControlException with sane jars with wsdd5.6 vm:

[jira] Commented: (DERBY-1547) Add svn version number to DatabaseMetaData getDatabaseProductVersion and getDriverVersion() to improve supportability

[ http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12434012 ] Deepa Remesh commented on DERBY-1547: - Hi Narayanan, I applied your DERBY-1547-sed.diff patch. I am also seeing the same failure seen by Kathey when running

[jira] Commented: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12433478 ] Deepa Remesh commented on DERBY-1522: - Thanks Mike for committing the patch. I would like this patch to be merged to 10.2. Merge command: svn merge -r

[jira] Updated: (DERBY-1585) derbylang/procedureInTrigger: not able to create trigger due to an open ResultSet

[ http://issues.apache.org/jira/browse/DERBY-1585?page=all ] Deepa Remesh updated DERBY-1585: Attachment: derby1585_v1.diff derby1585_v1.status Attaching a patch 'derby1585_v1.diff' to resolve the intermittent failure seen in the test

[jira] Closed: (DERBY-1698) Add more tests for Statement.setQueryTimeout method

[ http://issues.apache.org/jira/browse/DERBY-1698?page=all ] Deepa Remesh closed DERBY-1698. --- Add more tests for Statement.setQueryTimeout method --- Key: DERBY-1698 URL:

[jira] Updated: (DERBY-1698) Add more tests for Statement.setQueryTimeout method

[ http://issues.apache.org/jira/browse/DERBY-1698?page=all ] Deepa Remesh updated DERBY-1698: Fix Version/s: 10.2.1.0 10.3.0.0 Add more tests for Statement.setQueryTimeout method ---

[jira] Commented: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12433152 ] Deepa Remesh commented on DERBY-1522: - Thanks Dan for the suggestions. To try this, I used TestUtil methods for now. I'll open a Jira for adding shutdown

[jira] Created: (DERBY-1827) DatabasePropertyTestSetup.tearDown method gives exception when resetting properties

DatabasePropertyTestSetup.tearDown method gives exception when resetting properties --- Key: DERBY-1827 URL: http://issues.apache.org/jira/browse/DERBY-1827 Project:

[jira] Closed: (DERBY-1022) syscat.sql test failing due to change in size of a system table's column from VARCHAR(30) to VARCHAR(128)

[ http://issues.apache.org/jira/browse/DERBY-1022?page=all ] Deepa Remesh closed DERBY-1022. --- Resolution: Fixed Assignee: Satheesh Bandaram Closing the issue. Master files were updated by Satheesh. syscat.sql test failing due to change in size of

[jira] Updated: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ] Deepa Remesh updated DERBY-1522: Attachment: derby1522_v2.diff derby1522_v2.status Attaching a patch 'derby1522_v2.diff. It includes a JUnit test for testing the switch to SQL

[jira] Updated: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ] Deepa Remesh updated DERBY-1522: Derby Info: [Patch Available] Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[jira] Assigned: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ] Deepa Remesh reassigned DERBY-1522: --- Assignee: Deepa Remesh Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[jira] Updated: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ] Deepa Remesh updated DERBY-1522: Attachment: d1522_junit_v1.diff d1522_junit_v1.status I was trying to write a JUnit test case for this issue. The attached patch

[jira] Created: (DERBY-1807) Run more grant/revoke tests on an upgraded database

Run more grant/revoke tests on an upgraded database --- Key: DERBY-1807 URL: http://issues.apache.org/jira/browse/DERBY-1807 Project: Derby Issue Type: Test Components: Test

[jira] Resolved: (DERBY-1521) Upgrade test needs to be enhanced to test grant revoke

[ http://issues.apache.org/jira/browse/DERBY-1521?page=all ] Deepa Remesh resolved DERBY-1521. - Resolution: Fixed The following tests have been added to the upgrade test to test grant/revoke: * grant/revoke feature is not available in soft upgrade *

[jira] Commented: (DERBY-1551) Update documentation to indicate procedures can be called from triggers (DERBY-551)

[ http://issues.apache.org/jira/browse/DERBY-1551?page=comments#action_12431671 ] Deepa Remesh commented on DERBY-1551: - I think this change (svn revision 430925) missed the mega-merge. Can a committer please merge this doc change to 10.2

[jira] Updated: (DERBY-1551) Update documentation to indicate procedures can be called from triggers (DERBY-551)

[ http://issues.apache.org/jira/browse/DERBY-1551?page=all ] Deepa Remesh updated DERBY-1551: Fix Version/s: 10.2.1.0 Update documentation to indicate procedures can be called from triggers (DERBY-551)

[jira] Closed: (DERBY-1551) Update documentation to indicate procedures can be called from triggers (DERBY-551)

[ http://issues.apache.org/jira/browse/DERBY-1551?page=all ] Deepa Remesh closed DERBY-1551. --- Patch has been applied to trunk and 10.2 branch. Update documentation to indicate procedures can be called from triggers (DERBY-551)

[jira] Commented: (DERBY-1521) Upgrade test needs to be enhanced to test grant revoke

[ http://issues.apache.org/jira/browse/DERBY-1521?page=comments#action_12431750 ] Deepa Remesh commented on DERBY-1521: - Current state of this issue - after upgrade, we test basic grant/revoke works and system tables are updated correctly.

[jira] Updated: (DERBY-1698) Add more tests for Statement.setQueryTimeout method

[ http://issues.apache.org/jira/browse/DERBY-1698?page=all ] Deepa Remesh updated DERBY-1698: Attachment: derby-1698.diff derby-1698.status Attaching a patch 'derby-1698.diff' which adds an additional test to

[jira] Updated: (DERBY-1698) Add more tests for Statement.setQueryTimeout method

[ http://issues.apache.org/jira/browse/DERBY-1698?page=all ] Deepa Remesh updated DERBY-1698: Derby Info: [Patch Available] Add more tests for Statement.setQueryTimeout method --- Key:

[jira] Updated: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh updated DERBY-1582: Derby Info: [Patch Available] REVOKE statement does not generate a warning when no privileges are revoked.

[jira] Updated: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh updated DERBY-1582: Attachment: d1582_v2_with_tests.diff Attaching patch 'd1582_v2_with_tests.diff' which raises a warning when no privileges are revoked by the revoke statement

[jira] Updated: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh updated DERBY-1582: Derby Info: (was: [Patch Available]) With v2 patch, derbyall ran with no new failures. But the test additions conflict with changes in DERBY-1538.

[jira] Commented: (DERBY-1723) Database owner revokes select privilege from a schema owner but owner is still able to select

[ http://issues.apache.org/jira/browse/DERBY-1723?page=comments#action_12429048 ] Deepa Remesh commented on DERBY-1723: - I think this behaviour will be clearer if we raise a warning when no privileges are revoked. It will also solve the

[jira] Updated: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh updated DERBY-1582: Attachment: d1582_v2.diff d1582_v2.status Attaching a revised patch 'd1582_v2.diff' which raises a warning when no privileges are revoked by

[jira] Updated: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh updated DERBY-1582: Derby Info: [Patch Available] REVOKE statement does not generate a warning when no privileges are revoked.

[jira] Commented: (DERBY-1547) Add svn version number to DatabaseMetaData getDatabaseProductVersion and getDriverVersion() to improve supportability

[ http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12428414 ] Deepa Remesh commented on DERBY-1547: - Narayanan, Sorry for the confusion. I had seen the same failures which you reported when I ran derbyall in the new

[jira] Commented: (DERBY-1692) Client driver does not use the query timeout value set using Statement.setQueryTimeout() for subsequent executions using the same statement object

[ http://issues.apache.org/jira/browse/DERBY-1692?page=comments#action_12428454 ] Deepa Remesh commented on DERBY-1692: - Thanks Knut Anders for fixing this bug so quickly. I verified the patch solves this issue. And thanks for adding the

[jira] Commented: (DERBY-1705) Test jdbcapi/dataSourceReference.java fails with 10.2.1 beta candidate jars

[ http://issues.apache.org/jira/browse/DERBY-1705?page=comments#action_12428495 ] Deepa Remesh commented on DERBY-1705: - This diff is caused by the patch for DERBY-1130 which has been backed out from the trunk (as svn# 430891). This failure

[jira] Created: (DERBY-1707) Specifying an incorrect optimizer property (constraint=null) gives NullPointerException

Specifying an incorrect optimizer property (constraint=null) gives NullPointerException Key: DERBY-1707 URL: http://issues.apache.org/jira/browse/DERBY-1707

[jira] Updated: (DERBY-1130) Client should not allow databaseName to be set with setConnectionAttributes

[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ] Deepa Remesh updated DERBY-1130: Derby Info: [Patch Available, Existing Application Impact, Release Note Needed] (was: [Existing Application Impact, Release Note Needed]) Marking

[jira] Commented: (DERBY-1692) Client driver does not use the query timeout value set using Statement.setQueryTimeout() for subsequent executions using the same statement object

[ http://issues.apache.org/jira/browse/DERBY-1692?page=comments#action_12428163 ] Deepa Remesh commented on DERBY-1692: - This happens only with Statement class. It does not occur with PreparedStatement or CallableStatement objects. Client

[jira] Updated: (DERBY-1689) Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3

[ http://issues.apache.org/jira/browse/DERBY-1689?page=all ] Deepa Remesh updated DERBY-1689: Component/s: Regression Test Failure Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3

[jira] Closed: (DERBY-1697) Upgrade_10_1_10_2 test fails in tinderbox run in trunk

[ http://issues.apache.org/jira/browse/DERBY-1697?page=all ] Deepa Remesh closed DERBY-1697. --- Resolution: Duplicate I have added Regression Test Failure component to DERBY-1689. Marking this as duplicate. Upgrade_10_1_10_2 test fails in tinderbox run

[jira] Created: (DERBY-1698) Add more tests for Statement.setQueryTimeout method

Add more tests for Statement.setQueryTimeout method --- Key: DERBY-1698 URL: http://issues.apache.org/jira/browse/DERBY-1698 Project: Derby Issue Type: Test Components: Test

[jira] Assigned: (DERBY-1698) Add more tests for Statement.setQueryTimeout method

[ http://issues.apache.org/jira/browse/DERBY-1698?page=all ] Deepa Remesh reassigned DERBY-1698: --- Assignee: Deepa Remesh Add more tests for Statement.setQueryTimeout method --- Key:

[jira] Updated: (DERBY-1689) Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3

[ http://issues.apache.org/jira/browse/DERBY-1689?page=all ] Deepa Remesh updated DERBY-1689: Attachment: remove_10_2_upg_test.diff Attaching a patch 'remove_10_2_upg_test.diff' which removes the test Upgrade_10_1_10_2 from running in the trunk.

[jira] Created: (DERBY-1689) Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3

Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3 -- Key: DERBY-1689 URL: http://issues.apache.org/jira/browse/DERBY-1689 Project: Derby Issue

[jira] Created: (DERBY-1692) Client driver does not use the query timeout value set using Statement.setQueryTimeout() for subsequent executions using the same statement object

Client driver does not use the query timeout value set using Statement.setQueryTimeout() for subsequent executions using the same statement object --

[jira] Updated: (DERBY-1130) Client should not allow databaseName to be set with setConnectionAttributes

[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ] Deepa Remesh updated DERBY-1130: Attachment: d1130-test-dataSourceReference.diff d1130-test-dataSourceReference.status Thanks Sunitha, Kathey and David for looking at the

[jira] Updated: (DERBY-1130) Client should not allow databaseName to be set with setConnectionAttributes

[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ] Deepa Remesh updated DERBY-1130: Derby Info: [Patch Available, Existing Application Impact, Release Note Needed] (was: [Existing Application Impact, Release Note Needed]) Client should not

[jira] Commented: (DERBY-1551) Update documentation to indicate procedures can be called from triggers (DERBY-551)

[ http://issues.apache.org/jira/browse/DERBY-1551?page=comments#action_12427557 ] Deepa Remesh commented on DERBY-1551: - Laura, Thanks much for working on this. I went through the attached diff and html files and have couple of minor

[jira] Commented: (DERBY-1130) Client should not allow databaseName to be set with setConnectionAttributes

[ http://issues.apache.org/jira/browse/DERBY-1130?page=comments#action_12427597 ] Deepa Remesh commented on DERBY-1130: - I was going to post a release note about the existing application impact. But based on what Dan just said, this change

[jira] Updated: (DERBY-1130) Client should not allow databaseName to be set with setConnectionAttributes

[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ] Deepa Remesh updated DERBY-1130: Derby Info: [Existing Application Impact, Release Note Needed] (was: [Release Note Needed, Existing Application Impact, Patch Available]) As the current

[jira] Commented: (DERBY-1551) Update documentation to indicate procedures can be called from triggers (DERBY-551)

[ http://issues.apache.org/jira/browse/DERBY-1551?page=comments#action_12427623 ] Deepa Remesh commented on DERBY-1551: - The text I added is a different message for the same SQLState 42Z9D. So there can be two different messages in two

[jira] Commented: (DERBY-1551) Update documentation to indicate procedures can be called from triggers (DERBY-551)

[ http://issues.apache.org/jira/browse/DERBY-1551?page=comments#action_12427649 ] Deepa Remesh commented on DERBY-1551: - I went through the new html files and they look good to me. Thanks Laura. My +1 to commit patch derby1551_ref2.diff .

[jira] Created: (DERBY-1684) Move client data source tests from jdbcapi/dataSourceReference.java to a separate test

Move client data source tests from jdbcapi/dataSourceReference.java to a separate test -- Key: DERBY-1684 URL: http://issues.apache.org/jira/browse/DERBY-1684

[jira] Commented: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=comments#action_12427272 ] Deepa Remesh commented on DERBY-1582: - Thanks Satheesh for clarifying that we cannot revoke privileges from the database owner. I was reworking the patch and

[jira] Commented: (DERBY-1057) documentation to address Grant/Revoke (Derby-464)

[ http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12427289 ] Deepa Remesh commented on DERBY-1057: - Thanks Laura for addressing my comments. I looked at the updated html file rtunpropersqlauth.html for tuning guide and

[jira] Commented: (DERBY-1130) Client should not allow databaseName to be set with setConnectionAttributes

[ http://issues.apache.org/jira/browse/DERBY-1130?page=comments#action_12427330 ] Deepa Remesh commented on DERBY-1130: - Thanks Sunitha for looking at the patch. I moved updateDataSourceValues method call from getConnection to

[jira] Commented: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested

[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12427361 ] Deepa Remesh commented on DERBY-1522: - I had briefly looked at this task as I was working on DERBY-1521. I think we can cover the testing suggested by doing

[jira] Updated: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh updated DERBY-1582: Attachment: d1582_v1.diff d1582_v1.status Attaching a patch 'd1582_v1.diff' which raises a warning when no privileges are revoked by the

[jira] Assigned: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh reassigned DERBY-1582: --- Assignee: Deepa Remesh REVOKE statement does not generate a warning when no privileges are revoked.

[jira] Updated: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh updated DERBY-1582: Derby Info: [Patch Available] REVOKE statement does not generate a warning when no privileges are revoked.

[jira] Commented: (DERBY-1057) documentation to address Grant/Revoke (Derby-464)

[ http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12427035 ] Deepa Remesh commented on DERBY-1057: - Hi Laura, I only went through the updates in tuning guide. Please see my comments below: 1) It would be good to add

[jira] Updated: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh updated DERBY-1582: Derby Info: (was: [Patch Available]) Thanks Dan for looking at the patch. From what I had tried, I had found that we have to keep track if any privilege is

[jira] Commented: (DERBY-950) Add information to testing/README.htm about how to get connections in tests

[ http://issues.apache.org/jira/browse/DERBY-950?page=comments#action_12426620 ] Deepa Remesh commented on DERBY-950: Thanks Andrew for looking at this. My comments were based on the old method and may be soon outdated as we are moving to

[jira] Commented: (DERBY-1130) Client should not allow databaseName to be set with setConnectionAttributes

[ http://issues.apache.org/jira/browse/DERBY-1130?page=comments#action_12426683 ] Deepa Remesh commented on DERBY-1130: - Thanks David for revisiting this issue. I too got back to this only this week. Yesterday, I uploaded a new patch

[jira] Resolved: (DERBY-1544) Address remaining upgrade task(s) to complete full upgrade mechanism for GRANT/REVOKE, specifically with changing database owner name from 'DBA' to authorizationId of use

[ http://issues.apache.org/jira/browse/DERBY-1544?page=all ] Deepa Remesh resolved DERBY-1544. - Resolution: Fixed Address remaining upgrade task(s) to complete full upgrade mechanism for GRANT/REVOKE, specifically with changing database owner name

[jira] Commented: (DERBY-1521) Upgrade test needs to be enhanced to test grant revoke

[ http://issues.apache.org/jira/browse/DERBY-1521?page=comments#action_12426698 ] Deepa Remesh commented on DERBY-1521: - I found that after I change the existing test to use ij.connection.conn_name property, the test cannot be run with

[jira] Updated: (DERBY-1130) Client should not allow databaseName to be set with setConnectionAttributes

[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ] Deepa Remesh updated DERBY-1130: Attachment: d1130-client-v1.diff d1130-client-v1.status Attaching a patch 'd1130-client-v1.diff' which disallows databaseName attribute to be

[jira] Updated: (DERBY-1130) Client should not allow databaseName to be set with setConnectionAttributes

[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ] Deepa Remesh updated DERBY-1130: Fix Version/s: 10.2.0.0 Derby Info: [Patch Available] Client should not allow databaseName to be set with setConnectionAttributes

[jira] Commented: (DERBY-1544) Address remaining upgrade task(s) to complete full upgrade mechanism for GRANT/REVOKE, specifically with changing database owner name from 'DBA' to authorizationId of us

[ http://issues.apache.org/jira/browse/DERBY-1544?page=comments#action_12425981 ] Deepa Remesh commented on DERBY-1544: - The lists are used only in upgrade path - one for functions and other for procedures. The create path is directly

[jira] Commented: (DERBY-1544) Address remaining upgrade task(s) to complete full upgrade mechanism for GRANT/REVOKE, specifically with changing database owner name from 'DBA' to authorizationId of us

[ http://issues.apache.org/jira/browse/DERBY-1544?page=comments#action_12425767 ] Deepa Remesh commented on DERBY-1544: - Ran derbyall with 'd1544-patch2-v1.diff' using Sun jdk1.4.2 on Windows XP. No new failures. patch 1 and patch 2 are

[jira] Commented: (DERBY-1640) Instability in XATest

[ http://issues.apache.org/jira/browse/DERBY-1640?page=comments#action_12425795 ] Deepa Remesh commented on DERBY-1640: - If we look at the tinderbox results, this test started failing here:

[jira] Commented: (DERBY-1521) Upgrade test needs to be enhanced to test grant revoke

[ http://issues.apache.org/jira/browse/DERBY-1521?page=comments#action_12425881 ] Deepa Remesh commented on DERBY-1521: - Currently, only basic grant/revoke support is tested after upgrade. To run more grant/revoke tests after upgrade, I was

[jira] Commented: (DERBY-1057) documentation to address Grant/Revoke (Derby-464)

[ http://issues.apache.org/jira/browse/DERBY-1057?page=comments#action_12425886 ] Deepa Remesh commented on DERBY-1057: - For information on derby.database.sqlAuthorization property, this mail from Satheesh has some more information:

[jira] Commented: (DERBY-1521) Upgrade test needs to be enhanced to test grant revoke

[ http://issues.apache.org/jira/browse/DERBY-1521?page=comments#action_12425908 ] Deepa Remesh commented on DERBY-1521: - lang/grantRevokeDDL.sql test gets different connections as different users within the test . So I do not see a way

  1   2   3   4   5   6   7   >