[jira] Commented: (DERBY-1279) Bad column name in DatabaseMetaData.getColumns()

[ http://issues.apache.org/jira/browse/DERBY-1279?page=comments#action_12416715 ] Knut Anders Hatlen commented on DERBY-1279: --- As far as I can see, getColums() doesn't return any column named SCOPE_CATLOG or SCOPE_CATALOG (but it should return

[jira] Updated: (DERBY-1156) allow the encrypting of an existing unencrypted db and allow the re-encrypting of an existing encrypted db

[ http://issues.apache.org/jira/browse/DERBY-1156?page=all ] Suresh Thalamati updated DERBY-1156: Attachment: reencrypt_3.diff DERBY -1156 (partial) This patch adds some code required to support reconfigure(rencryption) of an already existing

Regression Test Failure! - Derby 415160 - Sun DBTG

[Auto-generated mail] *Derby* 415160/2006-06-18 19:46:38 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.6* 15715700 0 106.20% SunOS-5.10_i86pc-i386 Details in

[jira] Created: (DERBY-1427) sysinfo does not write Java SE and JDBC version when running under JDK 1.6

sysinfo does not write Java SE and JDBC version when running under JDK 1.6 -- Key: DERBY-1427 URL: http://issues.apache.org/jira/browse/DERBY-1427 Project: Derby Type: Bug Components: Tools

[jira] Updated: (DERBY-1341) LOB setBytes method(s) are currently no supported, but part of the Java 1.4 JDBC interface

[ http://issues.apache.org/jira/browse/DERBY-1341?page=all ] Anurag Shekhar updated DERBY-1341: -- Attachment: derby-1341.diff This diff is only for review of aprocah I am taking to resolve this issue. I have introduced 3 new class in this patch.

[jira] Created: (DERBY-1428) Generating derby properties on the fly can lead to non-deterministic engine startup behavior

Generating derby properties on the fly can lead to non-deterministic engine startup behavior Key: DERBY-1428 URL: http://issues.apache.org/jira/browse/DERBY-1428 Project: Derby

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

[ http://issues.apache.org/jira/browse/DERBY-1384?page=all ] Bernt M. Johnsen resolved DERBY-1384: - Resolution: Fixed Committed revision 415328. Increase default BLOB/CLOB length to maximum supported (2G?)

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

[ http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12416763 ] Bernt M. Johnsen commented on DERBY-1384: - Docs Committed revision 415329. Increase default BLOB/CLOB length to maximum supported (2G?)

[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] Created: (DERBY-1429) Additional vulnerability to non-deterministic startup behavior when applications generate derby properties on the fly

Additional vulnerability to non-deterministic startup behavior when applications generate derby properties on the fly - Key: DERBY-1429 URL:

[jira] Updated: (DERBY-1428) Generating derby properties on the fly can lead to non-deterministic engine startup behavior

[ http://issues.apache.org/jira/browse/DERBY-1428?page=all ] Rick Hillegas updated DERBY-1428: - Description: A Heisenbug can arise if more than one embedded Derby application runs in the same VM and at least one of them generates derby properties on

[jira] Commented: (DERBY-930) Add support for autoloading of Derby client drivers

[ http://issues.apache.org/jira/browse/DERBY-930?page=comments#action_12416775 ] Rick Hillegas commented on DERBY-930: - Adding a release note for this issue: PROBLEM If an embedded Derby application generates its own Derby properties on the fly, and

[jira] Commented: (DERBY-1429) Additional vulnerability to non-deterministic startup behavior when applications generate derby properties on the fly

[ http://issues.apache.org/jira/browse/DERBY-1429?page=comments#action_12416778 ] Rick Hillegas commented on DERBY-1429: -- We could separate out the booting of the engine from the registration of the embedded driver. This would eliminate this bug in

[jira] Commented: (DERBY-930) Add support for autoloading of Derby client drivers

[ http://issues.apache.org/jira/browse/DERBY-930?page=comments#action_12416781 ] Rick Hillegas commented on DERBY-930: - Here is a second rev of the release note. This attempts to clarify the extra exposure introduced by jdk1.6. PROBLEM If an embedded

Re: [jira] Commented: (DERBY-930) Add support for autoloading of Derby client drivers

Hi Bryan, Thanks for the quick response. I have revised the release note. Hopefully, it now describes the VM-specific issues better. Regards, -Rick Bryan Pendleton wrote: Rick Hillegas (JIRA) wrote: Adding a release note for this issue: Hi Rick, thanks for writing the release note.

Re: Driver autoloading and engine booting

Kathey Marsden wrote: David Van Couvering wrote: - Log a bug - Work on fixing it by booting on first connection rather than when the driver is loaded. It would be good to get input from the user community as well. One possible approach would be to log the bug, mark it as a regression,

Re: interested in working on DERBY-713

Hi Brent, Sounds like you're off to a good start. From the initial bug report, it looks like there's a good idea about which heuristic is being mis-applied here. Once you've studied the optimizer papers, I recommend that you post some high-level candidate solutions. Try to avoid optimizer

[jira] Assigned: (DERBY-1241) logmirror.ctrl is getting accessed outside the privileged block when the checkpoint instant is invalid on log factory boot method.

[ http://issues.apache.org/jira/browse/DERBY-1241?page=all ] Suresh Thalamati reassigned DERBY-1241: --- Assign To: Suresh Thalamati logmirror.ctrl is getting accessed outside the privileged block when the checkpoint instant is invalid on log

Re: Driver autoloading and engine booting

Jean T. Anderson wrote: Rick Hillegas wrote: Kathey Marsden wrote: David Van Couvering wrote: - Log a bug - Work on fixing it by booting on first connection rather than when the driver is loaded. It would be good to get input from the user community as well. One

Re: Driver autoloading and engine booting

Kathey Marsden wrote: Rick Hillegas wrote: I'm afraid I don't understand why we would want to revert our tests to the old behavior. It seems to me that our tests are practicing stunts which we strongly discourage: changing Derby properties on the fly. In general, there will always be

How to best handle variations in output from ij in sql tests?

I am working on reducing the number of tests failing when running with JDK 1.6. Some of the tests are now failing due to jdk16 specific master files that have not been updated after introduction of textual changes. To solve some of these failing tests I try eliminate the need for jdk16 specific

Re: Driver autoloading and engine booting

Rick Hillegas wrote: Jean T. Anderson wrote: Rick Hillegas wrote: ... Does the precedence for properties documentation need to be updated to mention jdbc 4/jdk 1.6 behavior? http://db.apache.org/derby/docs/dev/tuning/ctunsetprop23308.html I don't see that the precedence of properties has

[jira] Commented: (DERBY-578) Grouped select from temporary table raises null pointer exception in byte code generator

[ http://issues.apache.org/jira/browse/DERBY-578?page=comments#action_12416803 ] Rick Hillegas commented on DERBY-578: - Thanks, Manish. As you said, the fix looks pretty simple. I'm running regression tests now. I have a couple questions: 1) I don't

Re: How to best handle variations in output from ij in sql tests?

Hi Olav, Thanks for digging into this. The differences in the embedded output are caused by JDBC4's introduction of SQLException subclasses. These now replace Derby's hand-rolled subclass of SQLException. The old Derby subclass overrode the getMessage() method. That's why you used to see

[jira] Commented: (DERBY-1428) Generating derby properties on the fly can lead to non-deterministic engine startup behavior

[ http://issues.apache.org/jira/browse/DERBY-1428?page=comments#action_12416810 ] Rick Hillegas commented on DERBY-1428: -- Kathey adds the following: I think DERBY-1428 and DERBY-149 are not really related to generating derby.properties on the fly

Re: Driver autoloading and engine booting

Jean T. Anderson wrote: Rick Hillegas wrote: Jean T. Anderson wrote: Rick Hillegas wrote: ... Does the precedence for properties documentation need to be updated to mention jdbc 4/jdk 1.6 behavior? http://db.apache.org/derby/docs/dev/tuning/ctunsetprop23308.html I don't see that the

[jira] Commented: (DERBY-1338) Client tests DerbyNetNewServer and NSinSameVM fail with NoClassDefFoundError: DRDAProtocolExceptionInfo when run from classes dir

[ http://issues.apache.org/jira/browse/DERBY-1338?page=comments#action_12416817 ] Dag H. Wanvik commented on DERBY-1338: -- From: Bryan Pendleton, Date: Tue, 23 May 2006 16:17:59 -0700 The shutdown of the server *has* interrupted the thread, in

[jira] Updated: (DERBY-1338) Client tests DerbyNetNewServer and NSinSameVM fail with NoClassDefFoundError: DRDAProtocolExceptionInfo when run from classes dir

[ http://issues.apache.org/jira/browse/DERBY-1338?page=all ] Dag H. Wanvik updated DERBY-1338: - Attachment: derby-1338.stat derby-1338.diff Here is a simple patch which preloads the class causing the problem. It makes the tests run

[jira] Commented: (DERBY-1108) The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5

[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12416823 ] A B commented on DERBY-1108: I'm not very well acquainted with this code, but based on the example of escape analysis posted by the JVM team, I think I understand why this test

[jira] Commented: (DERBY-1108) The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5

[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12416825 ] Kathey Marsden commented on DERBY-1108: --- Thanks Army for the comment. I think I understand escape analysis better now and how it relatest to this issue and I think 1)

[jira] Updated: (DERBY-1338) Client tests DerbyNetNewServer and NSinSameVM fail with NoClassDefFoundError: DRDAProtocolExceptionInfo when run from classes dir

[ http://issues.apache.org/jira/browse/DERBY-1338?page=all ] Dag H. Wanvik updated DERBY-1338: - Derby Info: [Patch Available] Client tests DerbyNetNewServer and NSinSameVM fail with NoClassDefFoundError: DRDAProtocolExceptionInfo when run from

[jira] Updated: (DERBY-1338) Client tests DerbyNetNewServer and NSinSameVM fail with NoClassDefFoundError: DRDAProtocolExceptionInfo when run from classes dir

[ http://issues.apache.org/jira/browse/DERBY-1338?page=all ] Dag H. Wanvik updated DERBY-1338: - Component: Network Server (was: Regression Test Failure) Environment: Sun JDK 1.4.2, Sun JDK 1.5 on Solaris was: Sun JDK

Re: Driver autoloading and engine booting

Rick Hillegas wrote: This topic was raised in an earlier email thread (http://comments.gmane.org/gmane.comp.apache.db.derby.devel/20899) but it does not appear that we agreed on a solution. I would like to re-open this topic and hopefully we can converge on how we want to handle this issue.

Re: interested in working on DERBY-713

Hiya Rick, Thanks for you helpful reply! I spent some time over the weekend snooping around (mostly) InListOperatorNode and OptimizerImpl, but never found out _where_ the table scan was chosen over an index scan for finding the IN matches...I really wanted to find it before begging for

[jira] Commented: (DERBY-1338) Client tests DerbyNetNewServer and NSinSameVM fail with NoClassDefFoundError: DRDAProtocolExceptionInfo when run from classes dir

[ http://issues.apache.org/jira/browse/DERBY-1338?page=comments#action_12416840 ] Bryan Pendleton commented on DERBY-1338: Hi Dag, I looked at your patch. Unless anybody else has a better suggestion, I think we should go ahead and use your patch,