[jira] Updated: (DERBY-939) NullPointerException at ResultSet.close() time for simple query using UNION and INTERSECT

[ http://issues.apache.org/jira/browse/DERBY-939?page=all ] Yip Ng updated DERBY-939: - Derby Info: [Patch Available, Release Note Needed] NullPointerException at ResultSet.close() time for simple query using UNION and INTERSECT

[jira] Resolved: (DERBY-1446) Derby can enter infinite loop and consume 100% cpu when loading class when running a stored procedure within Eclipse 3.2

[ http://issues.apache.org/jira/browse/DERBY-1446?page=all ] Kathey Marsden resolved DERBY-1446. --- Resolution: Fixed Assignee: Kathey Marsden The eclipse issue that the ContextFinder can enter in infinite loop while delegating to other

[jira] Closed: (DERBY-1446) Derby can enter infinite loop and consume 100% cpu when loading class when running a stored procedure within Eclipse 3.2

[ http://issues.apache.org/jira/browse/DERBY-1446?page=all ] Kathey Marsden closed DERBY-1446. - Assignee: (was: Kathey Marsden) Derby can enter infinite loop and consume 100% cpu when loading class when running a stored procedure within Eclipse

[jira] Created: (DERBY-1579) Remove SYS.SYSREQUIREDPERMS from Derby 10.2. This was added for Grant Revoke functionality

Remove SYS.SYSREQUIREDPERMS from Derby 10.2. This was added for Grant Revoke functionality -- Key: DERBY-1579 URL: http://issues.apache.org/jira/browse/DERBY-1579

[jira] Assigned: (DERBY-1571) NetworkServerControlImpl.consoleExceptionPrintTrace() prints stack trace even when logWriter is null

[ http://issues.apache.org/jira/browse/DERBY-1571?page=all ] Knut Anders Hatlen reassigned DERBY-1571: - Assignee: Knut Anders Hatlen NetworkServerControlImpl.consoleExceptionPrintTrace() prints stack trace even when logWriter is null

[jira] Updated: (DERBY-1543) Address two remaining issues with GRANT/REVOKE functionality: 1) Add warning when sqlAuthorization is on with authentication off 2) Drop permission descriptors when object

[ http://issues.apache.org/jira/browse/DERBY-1543?page=all ] Satheesh Bandaram updated DERBY-1543: - Attachment: DERBY-1543.out This (temp) patch addresses both these remaining issues. Some work is needed to complete this patch... including 1)

[jira] Assigned: (DERBY-1538) Unexpected behavior on self privilege revocation

[ http://issues.apache.org/jira/browse/DERBY-1538?page=all ] Satheesh Bandaram reassigned DERBY-1538: Assignee: Satheesh Bandaram Unexpected behavior on self privilege revocation

[jira] Updated: (DERBY-1579) Remove SYS.SYSREQUIREDPERM from Derby 10.2. This was added for Grant Revoke functionality

[ http://issues.apache.org/jira/browse/DERBY-1579?page=all ] Mamta A. Satoor updated DERBY-1579: --- Summary: Remove SYS.SYSREQUIREDPERM from Derby 10.2. This was added for Grant Revoke functionality (was: Remove SYS.SYSREQUIREDPERMS from Derby 10.2.

[jira] Commented: (DERBY-1296) Setting property derby.system.bootAll causes an Exception

[ http://issues.apache.org/jira/browse/DERBY-1296?page=comments#action_12423000 ] Andreas Korneliussen commented on DERBY-1296: - Thanks for making the patch for this critical issue. It seems there is a conflict when applying it, due

Regression Test Failure! - Derby 424770 - Sun DBTG

[Auto-generated mail] *Derby* 424770/2006-07-23 19:46:10 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.6* NA NA NANA SunOS-5.10_i86pc-i386 Details in

Are separate JDBC 4.0 versions of the DataSource classes really needed?

Hi, I started looking at our implementation of JDBC 4.0 data sources when I saw Rick updating the documentation with information about using Embedded*DataSource40 when running jvm=1.6. I think it is problematic to have this split between pre-JDBC4 data sources and JDBC4 data sources for a number

[jira] Updated: (DERBY-1571) NetworkServerControlImpl.consoleExceptionPrintTrace() prints stack trace even when logWriter is null

[ http://issues.apache.org/jira/browse/DERBY-1571?page=all ] Knut Anders Hatlen updated DERBY-1571: -- Attachment: 1571.diff 1571.diff changes NetworkServerControlImpl so that it doesn't print stack traces when logWriter is null. Derbyall runs

[jira] Updated: (DERBY-1571) NetworkServerControlImpl.consoleExceptionPrintTrace() prints stack trace even when logWriter is null

[ http://issues.apache.org/jira/browse/DERBY-1571?page=all ] Knut Anders Hatlen updated DERBY-1571: -- Derby Info: [Patch Available] NetworkServerControlImpl.consoleExceptionPrintTrace() prints stack trace even when logWriter is null

[jira] Updated: (DERBY-1296) Setting property derby.system.bootAll causes an Exception

[ http://issues.apache.org/jira/browse/DERBY-1296?page=all ] Fernanda Pizzorno updated DERBY-1296: - Attachment: derby-1296v2.diff derby-1296v2.stat The conflics are resolved and the test is renamed from bootAllTest to BootAllTest in

[jira] Updated: (DERBY-815) Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()

[ http://issues.apache.org/jira/browse/DERBY-815?page=all ] Dyre Tjeldvoll updated DERBY-815: - Attachment: derby-815.v4.diff derby-815.v4.stat derbyall_report.v4.txt Attaching new patch (v4) based on revision 425020.

[jira] Updated: (DERBY-815) Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()

[ http://issues.apache.org/jira/browse/DERBY-815?page=all ] Dyre Tjeldvoll updated DERBY-815: - Derby Info: [Patch Available] Setting patch available for the v4 patch. Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()

[jira] Commented: (DERBY-550) BLOB : java.lang.OutOfMemoryError with network JDBC driver (org.apache.derby.jdbc.ClientDriver)

[ http://issues.apache.org/jira/browse/DERBY-550?page=comments#action_12423067 ] Tomohito Nakayama commented on DERBY-550: - I confirmed that the BlobOutOfMem.java ran without error in next configuration, after the patch of DERBY-1513

[jira] Created: (DERBY-1580) jdbcapi/SURQueryMixTest.junit: Error connecting to server, Address already in use on Solaris sparc (zones)

jdbcapi/SURQueryMixTest.junit: Error connecting to server, Address already in use on Solaris sparc (zones) -- Key: DERBY-1580 URL:

Re: [jira] Commented: (DERBY-1377) Update copyright headers to comply with new ASF policy

We are about 3 weeks away from generating a release candidate which must conform to a new, murky policy. These options occur to me: 1) Generate a release which follows the old policy. I would imagine that the DB PMC would feel bound to reject such a release. 2) Wait for the policy to sort

Re: remaining 10.2 blocker

Hi Kathey, If an issue would cause you to vote -1 on the 10.2 release, please mark the issue as Critical or Blocker. Kathey Marsden wrote: Kathey Marsden wrote: Alternately we could just not muddy the Jira descriptions of these fields and only mark only mark Fix Version 10.2 for an

[jira] Updated: (DERBY-1227) Network Server should not use the underlying embedded prepared statement when accessing a BrokeredPreparedStatement

[ http://issues.apache.org/jira/browse/DERBY-1227?page=all ] Mike Matrigali updated DERBY-1227: -- Fix Version/s: 10.1.4.0 committed patch to 10.1 branch: m101_142:117svn commit Sendingjava\drda\org\apache\derby\impl\drda\DRDAConnThread.java

Re: Are separate JDBC 4.0 versions of the DataSource classes really needed?

Hi Knut Anders, I don't understand part of your experiment. The implementation of createQueryObject() refers to another class, QueryObjectFactory, which was introduced by JDK 1.6. How did EmbeddedDataSource compile with this reference? Thanks, -Rick Knut Anders Hatlen wrote: Hi, I

Re: Are separate JDBC 4.0 versions of the DataSource classes really needed?

Rick Hillegas [EMAIL PROTECTED] writes: Hi Knut Anders, I don't understand part of your experiment. The implementation of createQueryObject() refers to another class, QueryObjectFactory, which was introduced by JDK 1.6. How did EmbeddedDataSource compile with this reference? We need to use

[jira] Created: (DERBY-1581) DependencyMangerImpl re-loads the Provider multiple times from the DataDictionary when loading the stored dependencies for the Provider.

DependencyMangerImpl re-loads the Provider multiple times from the DataDictionary when loading the stored dependencies for the Provider. Key:

[jira] Updated: (DERBY-1581) BasicDependencyManager re-loads the Provider multiple times from the DataDictionary when loading the stored dependencies for the Provider.

[ http://issues.apache.org/jira/browse/DERBY-1581?page=all ] Daniel John Debrunner updated DERBY-1581: - Summary: BasicDependencyManager re-loads the Provider multiple times from the DataDictionary when loading the stored dependencies for the

[jira] Closed: (DERBY-1227) Network Server should not use the underlying embedded prepared statement when accessing a BrokeredPreparedStatement

[ http://issues.apache.org/jira/browse/DERBY-1227?page=all ] Sunitha Kambhampati closed DERBY-1227. -- Ran tests and verified the fix is in 10.1 as well as 10.2, so closing this issue. Network Server should not use the underlying embedded prepared

Build failure? (Re: svn commit: r425116 - /db/derby/code/trunk/java/engine/org/apache/derby/iapi/sql/dictionary/)

I just did a sync, ant clobber, ant all and the build is failing with the following error: [javac] Compiling 7 source files to C:\p4clients\main_codeline\classes [javac]

Re: Build failure? (Re: svn commit: r425116 - /db/derby/code/trunk/java/engine/org/apache/derby/iapi/sql/dictionary/)

Army wrote: I just did a sync, ant clobber, ant all and the build is failing with the following error: Sorry, my fault - just committed a fix (I hope). Dan.

Re: Build failure? (Re: svn commit: r425116 - /db/derby/code/trunk/java/engine/org/apache/derby/iapi/sql/dictionary/)

Daniel John Debrunner wrote: I just did a sync, ant clobber, ant all and the build is failing with the following error: Sorry, my fault - just committed a fix (I hope). Yep, I just did a full clobber/rebuild and all is well again. Thanks! Army

Re: Build failure? (Re: svn commit: r425116 - /db/derby/code/trunk/java/engine/org/apache/derby/iapi/sql/dictionary/)

I just resync and did a rebuild, its fine now.

[jira] Commented: (DERBY-1543) Address two remaining issues with GRANT/REVOKE functionality: 1) Add warning when sqlAuthorization is on with authentication off 2) Drop permission descriptors when obje

[ http://issues.apache.org/jira/browse/DERBY-1543?page=comments#action_12423133 ] Daniel John Debrunner commented on DERBY-1543: -- How does the dropping of permission descriptors relate to the permission cache? In this code it seems

[jira] Commented: (DERBY-1535) Trial 2 for DERBY-550, improve use of Engine from NetworkServer and reduce memory usage

[ http://issues.apache.org/jira/browse/DERBY-1535?page=comments#action_12423134 ] Sunitha Kambhampati commented on DERBY-1535: Hi Tomohito, Thanks for looking into this issue. I noticed, there are some differences in the master file

[jira] Updated: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=all ] Rick Hillegas updated DERBY-1271: - Attachment: derby-1271_refGuide_v01.diff derby-1271_refGuide_v01.tar Attaching relevant changes to the Reference Guide

[jira] Updated: (DERBY-1373) Encrypted databases cannot be booted using the jar subprotocol (and possibly also using http/https/classpath)

[ http://issues.apache.org/jira/browse/DERBY-1373?page=all ] Mike Matrigali updated DERBY-1373: -- Committed the 10.1_explicitsvnadd_derby1373.diff.txt patch to the 10.1 branch: m101_142:149svn commit Sending

[jira] Updated: (DERBY-1373) Encrypted databases cannot be booted using the jar subprotocol (and possibly also using http/https/classpath)

[ http://issues.apache.org/jira/browse/DERBY-1373?page=all ] Mike Matrigali updated DERBY-1373: -- Fix Version/s: 10.1.4.0 Encrypted databases cannot be booted using the jar subprotocol (and possibly also using http/https/classpath)

[jira] Updated: (DERBY-1373) Encrypted databases cannot be booted using the jar subprotocol (and possibly also using http/https/classpath)

[ http://issues.apache.org/jira/browse/DERBY-1373?page=all ] Sunitha Kambhampati updated DERBY-1373: --- Fix Version/s: 10.1.3.2 Adding fix version 10.1.3.2 Encrypted databases cannot be booted using the jar subprotocol (and possibly also using

[jira] Assigned: (DERBY-936) Main branch docs display version as 10.1, should be 10.2.

[ http://issues.apache.org/jira/browse/DERBY-936?page=all ] Rick Hillegas reassigned DERBY-936: --- Assignee: Rick Hillegas Main branch docs display version as 10.1, should be 10.2. -

[jira] Updated: (DERBY-1319) Need documentation on the toursdb demo database

[ http://issues.apache.org/jira/browse/DERBY-1319?page=all ] Myrna van Lunteren updated DERBY-1319: -- Summary: Need documentation on the toursdb demo database (was: Need documentation on the toursdb schema.) In fact, we need to document the entire

Hard upgrade issues for 10.2

GRANT/REVOKE requires catalog support and so won't be available to users who soft-upgrade to 10.2. Are there other 10.2 features which will not be available after soft upgrade? Thanks, -Rick

Regression Test Failure! - TinderBox_Derby 425133 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 425133/2006-07-24 19:42:40 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 6679673 2 148.73% SunOS-5.10_i86pc-i386 Details in

[jira] Assigned: (DERBY-1319) Need documentation on the toursdb demo database

[ http://issues.apache.org/jira/browse/DERBY-1319?page=all ] Myrna van Lunteren reassigned DERBY-1319: - Assignee: Myrna van Lunteren Need documentation on the toursdb demo database ---

[jira] Assigned: (DERBY-1027) encodingTests suite cannot be run on JDK 1.4.2

[ http://issues.apache.org/jira/browse/DERBY-1027?page=all ] Myrna van Lunteren reassigned DERBY-1027: - Assignee: Myrna van Lunteren encodingTests suite cannot be run on JDK 1.4.2 --

[jira] Updated: (DERBY-1537) Boot-time exception when running Derby tests with derbytools.jar in front of derby.jar in the classpath.

[ http://issues.apache.org/jira/browse/DERBY-1537?page=all ] Kathey Marsden updated DERBY-1537: -- Component/s: SQL (was: Test) Fix Version/s: 10.2.0.0 Priority: Critical (was: Minor) Changing this to Critical and

[jira] Updated: (DERBY-1564) wisconsin.sql test failed in DerbyNet framework, VM for network server got OutOfMemoryError

[ http://issues.apache.org/jira/browse/DERBY-1564?page=all ] Kathey Marsden updated DERBY-1564: -- Priority: Critical (was: Major) Raising this to critcial and Fix Version 10.2. I think we need to resolve whether the increased memory usage for this

[jira] Resolved: (DERBY-1532) Add GRANTOR column to primary key for SYSTABLEPERMS, SYSCOLPERMS and SYSROUTINEPERMS

[ http://issues.apache.org/jira/browse/DERBY-1532?page=all ] Satheesh Bandaram resolved DERBY-1532. -- Resolution: Invalid As mentioned, GRANTOR is already part of the primary key in all three new system catalogs. Information in the functional spec

[jira] Closed: (DERBY-1532) Add GRANTOR column to primary key for SYSTABLEPERMS, SYSCOLPERMS and SYSROUTINEPERMS

[ http://issues.apache.org/jira/browse/DERBY-1532?page=all ] Satheesh Bandaram closed DERBY-1532. Add GRANTOR column to primary key for SYSTABLEPERMS, SYSCOLPERMS and SYSROUTINEPERMS

[jira] Assigned: (DERBY-1320) Test lang/procedure.java fails with ibm1.5 jvm

[ http://issues.apache.org/jira/browse/DERBY-1320?page=all ] Manjula Kutty reassigned DERBY-1320: Assignee: Manjula Kutty Test lang/procedure.java fails with ibm1.5 jvm -- Key:

[jira] Updated: (DERBY-1257) Enhance Derby optimizer and execution model to support effective use of multiple indexes on one table. Derby currently can use one index on a table and there are many situ

[ http://issues.apache.org/jira/browse/DERBY-1257?page=all ] Kathey Marsden updated DERBY-1257: -- Fix Version/s: 10.3.0.0 (was: 10.2.0.0) Since this remains unassigned I don't think it reasonable to think someone will pick it up

[jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

[ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12423188 ] Kathey Marsden commented on DERBY-1252: --- This issue is a regression. It would be ideal to release Derby 10.2 without any known regressions so we don't

[jira] Updated: (DERBY-1581) BasicDependencyManager re-loads the Provider multiple times from the DataDictionary when loading the stored dependencies for the Provider.

[ http://issues.apache.org/jira/browse/DERBY-1581?page=all ] Daniel John Debrunner updated DERBY-1581: - Attachment: derby1581_draft.txt Proposed patch - only had limited testing so far. Will test using derbyall BasicDependencyManager re-loads

[jira] Commented: (DERBY-1252) Old clients with new server return wrong database metadata values for some methods

[ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12423191 ] Daniel John Debrunner commented on DERBY-1252: -- How would this regression manifest itself in a working application? Old clients with new server

[jira] Commented: (DERBY-813) Clean up coding error in searchClauseTransitiveClosure method in PredicateList.java

[ http://issues.apache.org/jira/browse/DERBY-813?page=comments#action_12423193 ] Kathey Marsden commented on DERBY-813: -- I do not really understand the functional impact of this issue, so don't know if it is good to target for 10.2 or not

[jira] Updated: (DERBY-464) Enhance Derby by adding grant/revoke support. Grant/Revoke provide finner level of privileges than currently provided by Derby that is especially useful in network configur

[ http://issues.apache.org/jira/browse/DERBY-464?page=all ] Satheesh Bandaram updated DERBY-464: Attachment: grantRevokeSpec_v3.html Updated functional spec... Changes from v2 version are: 1) Added GRANTOR column to primary key to new system

[jira] Commented: (DERBY-528) Support for DRDA Strong User ID and Password Substitute Authentication (USRSSBPWD) scheme

[ http://issues.apache.org/jira/browse/DERBY-528?page=comments#action_12423196 ] Francois Orsini commented on DERBY-528: --- I have run against several JVM's versions and I have not encountered this symptom thus far - It's probably due to

Re: [jira] Updated: (DERBY-883) Enhance GROUP BY clause to support expressions instead of just column references.

Hi Manish, I have to be honest and say that I haven't taken the time to fully understand the guts of this patch--namely, the part where you rewrite the group-by tree in GroupByNode.addAggregateColumns(). But I did do some review of the overall patch and I have the following comments. If you

[jira] Commented: (DERBY-464) Enhance Derby by adding grant/revoke support. Grant/Revoke provide finner level of privileges than currently provided by Derby that is especially useful in network config

[ http://issues.apache.org/jira/browse/DERBY-464?page=comments#action_12423197 ] Satheesh Bandaram commented on DERBY-464: - Should this issue be marked as RESOLVED? This JIRA entry covers main GRANT/REVOKE functionality being developed.

[jira] Updated: (DERBY-464) Enhance Derby by adding grant/revoke support. Grant/Revoke provide finner level of privileges than currently provided by Derby that is especially useful in network configur

[ http://issues.apache.org/jira/browse/DERBY-464?page=all ] Satheesh Bandaram updated DERBY-464: Fix Version/s: 10.2.0.0 Enhance Derby by adding grant/revoke support. Grant/Revoke provide finner level of privileges than currently provided by

Jira Derby Info flags meaning WAS Re: [jira] Commented: (DERBY-1252) ...

Is there any definition on what these Jira 'Derby Info' flags mean? Regression Existing Application Impact To me they mean the same thing. Dan. Daniel John Debrunner (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1252?page=comments#action_12423191 ] Daniel

[jira] Commented: (DERBY-1543) Address two remaining issues with GRANT/REVOKE functionality: 1) Add warning when sqlAuthorization is on with authentication off 2) Drop permission descriptors when obje

[ http://issues.apache.org/jira/browse/DERBY-1543?page=comments#action_12423198 ] Satheesh Bandaram commented on DERBY-1543: -- Good point, Dan. I will address this in my final version of the patch. Address two remaining issues with

[jira] Commented: (DERBY-464) Enhance Derby by adding grant/revoke support. Grant/Revoke provide finner level of privileges than currently provided by Derby that is especially useful in network config

[ http://issues.apache.org/jira/browse/DERBY-464?page=comments#action_12423202 ] Daniel John Debrunner commented on DERBY-464: - I would say one definition of sub-task is that the main task is not complete until all of the sub-tasks

Re: [jira] Updated: (DERBY-883) Enhance GROUP BY clause to support expressions instead of just column references.

Army wrote: Nit-picking: Changes that you don't *have* to do but that might help in cleaning up the patch. A. Unnecessary white-space changes? +1 to avoiding such changes. In SelectNode.java: - VerifyAggregateExpressionsVisitor visitor = - new

[jira] Resolved: (DERBY-1023) Add EXTERNAL SECURITY DEFINER and EXTERNAL SECURITY INVOKER support for routines(functions or procedures)

[ http://issues.apache.org/jira/browse/DERBY-1023?page=all ] Satheesh Bandaram resolved DERBY-1023. -- Resolution: Won't Fix Not part of the functional spec being targetted for 10.2 release. Might still be useful enhancement to Derby. If someone has

[jira] Closed: (DERBY-1023) Add EXTERNAL SECURITY DEFINER and EXTERNAL SECURITY INVOKER support for routines(functions or procedures)

[ http://issues.apache.org/jira/browse/DERBY-1023?page=all ] Satheesh Bandaram closed DERBY-1023. Add EXTERNAL SECURITY DEFINER and EXTERNAL SECURITY INVOKER support for routines(functions or procedures)

[jira] Assigned: (DERBY-1543) Address two remaining issues with GRANT/REVOKE functionality: 1) Add warning when sqlAuthorization is on with authentication off 2) Drop permission descriptors when objec

[ http://issues.apache.org/jira/browse/DERBY-1543?page=all ] Satheesh Bandaram reassigned DERBY-1543: Assignee: Satheesh Bandaram I have a patch that is partial. Will post final complete patch soon. Address two remaining issues with

Re: Jira Derby Info flags meaning WAS Re: [jira] Commented: (DERBY-1252) ...

Daniel John Debrunner wrote: Is there any definition on what these Jira 'Derby Info' flags mean? Regression A Derby product regression that is a bug that hopefully will be fixed. Example DERBY-1459 Existing Application Impact Any change intentional or otherwise that might affect

Regression Test Failure! - TinderBox_Derby 425185 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 425185/2006-07-24 23:03:17 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 6679673 2 146.10% SunOS-5.10_i86pc-i386 Details in

Concerned about the 'Insufficient data while reading from network error' in regression tests.

Looking at http://www.multinet.no/~solberg/public/Apache/Derby/Limited/, there are a number of failures on the daily regression tests, there are some network server tests that fail with this exception. FAIL -- unexpected exception SQLSTATE(58009):java.sql.SQLException: Insufficient data

Re: Regression Test Failure! - Derby 424609 - Sun DBTG

http://www.multinet.no/~solberg/public/Apache/Derby/testlog/CYGWIN_NT-5.2_i686-unknown/424402-derbyall_diff.txt I see the encryptionKey_jar.sql test failing on jdk15/cygwin on ole's test machines. This test was added as part of derby-1373 recently. This test passed on the tinderbox runs and

[jira] Commented: (DERBY-1537) Boot-time exception when running Derby tests with derbytools.jar in front of derby.jar in the classpath.

[ http://issues.apache.org/jira/browse/DERBY-1537?page=comments#action_12423212 ] Andrew McIntyre commented on DERBY-1537: This problem only occurs when running with the security manager enabled. The underlying problem is that there is

[jira] Assigned: (DERBY-1537) Boot-time exception when running Derby tests with derbytools.jar in front of derby.jar in the classpath.

[ http://issues.apache.org/jira/browse/DERBY-1537?page=all ] Andrew McIntyre reassigned DERBY-1537: -- Assignee: Andrew McIntyre Boot-time exception when running Derby tests with derbytools.jar in front of derby.jar in the classpath.

Re: [jira] Updated: (DERBY-883) Enhance GROUP BY clause to support expressions instead of just column references.

Army, Thanks for the feeback. I appreciate it. You've identified atleast one (perhaps 2) bugs with my code changes. On the point of 80 chars per line, I can't help but ask: does a tab count as 4 chars or 8? The conventional wisdom from an earlier discussion was that you set your editor to treat

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

REVOKE statement does not generate a warning when no privileges are revoked. Key: DERBY-1582 URL: http://issues.apache.org/jira/browse/DERBY-1582 Project: Derby