Regression Test Failure! - Derby 430835 - Sun DBTG

[Auto-generated mail] *Derby* 430835/2006-08-11 19:46:10 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* NA NA NANA CYGWIN_NT-5.1_i686-unknown 7691684 2 121.89%

[jira] Subscription: Derby: JIRA issues with patch available

Issue Subscription Filter: Derby: JIRA issues with patch available (18 issues) Subscriber: derby-dev Key Summary DERBY-1681 Regression (wrong results): Join predicate can be ignored for left-most child in a chain of nested unions. http://issues.apache.org/jira/browse/DERBY-1

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

[ http://issues.apache.org/jira/browse/DERBY-1684?page=comments#action_12427699 ] Daniel John Debrunner commented on DERBY-1684: -- Why not keep the code in a single place and have the test self-configure. Decide which classes to test

Re: [VOTE] Approve coding conventions for the Derby project

Kathey Marsden wrote: > This is a vote to define the coding conventions for the Derby project > per the db project guidelines http://db.apache.org/source.html > Vote closes 10:00am, Wednesday, August 15. timezone? Dan.

Re: [VOTE] Approve coding conventions for the Derby project

Daniel John Debrunner wrote: timezone? If we need a timezone, we can go by my watch which would be: Vote closes 10:00am PST, Wednesday, August 16. I usually just loiter to post the results, past the designated time anywhere in the world #:) Kathey

[jira] Updated: (DERBY-634) Subquery materialization can cause stack overflow

[ http://issues.apache.org/jira/browse/DERBY-634?page=all ] Satheesh Bandaram updated DERBY-634: Attachment: DERBY-634.diff This patch addresses stack overflow by preventing bad cases of subquery optimization. However, extending subquery materializa

[VOTE] Approve coding conventions for the Derby project

[+1]  Adopt the coding convention described.Craig This is a vote to define the coding conventions for the Derby project per the db project guidelines http://db.apache.org/source.html Vote closes  10:00am, Wednesday, August  15. [+1]  Adopt the coding convention described. [-1 ] Do not adopt the co

[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-v2.diff d1130-v2.status Attaching a patch 'd1130-v2.diff' which ensures that database name set using setConnectionAttributes

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

[ http://issues.apache.org/jira/browse/DERBY-1684?page=comments#action_12427726 ] Deepa Remesh commented on DERBY-1684: - Yes, we can add conditions to run specific tests based on the framework. In case of jdbcapi/dataSourceReference.java tes

[jira] Updated: (DERBY-415) sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing

[ http://issues.apache.org/jira/browse/DERBY-415?page=all ] Bryan Pendleton updated DERBY-415: -- Attachment: derby-415-cp-db2driver.diff I think that Andrew's idea about adding a new argument: '-cp db2driver' is a very good one. Attached is derby-415-c

10.2 Buddy Testing wiki up

Hello,The 10.2 Buddy Testing wiki is available at:http://wiki.apache.org/db-derby/TenTwoBuddyTesting A link is also provided from the main 10.2 release page at:http://wiki.apache.org/db-derby/TenTwoReleaseEverybody is highly encouraged to sign up for multiple 10.2 features. Please add your commen

Re: 10.2.1.0 beta candidate available for testing

Rick Hillegas wrote: Please test-drive the 10.2.1.0 beta candidate, available at http://people.apache.org/~rhillegas/10.2.1.0-beta/. I have a probably very foolish question. By beta "candidate" does that mean that this is something we vote on to reach beta status ala the the HTTP Server pr