From gavinpatel@example.net Thu Feb 01 10:46:27 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 99711 invoked from network); 1 Feb 2007 10:46:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 10:46:27 -0000 Received: (qmail 1358 invoked by uid 500); 1 Feb 2007 10:46:33 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 1148 invoked by uid 500); 1 Feb 2007 10:46:32 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 1139 invoked by uid 99); 1 Feb 2007 10:46:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 02:46:32 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 02:46:26 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id BDC5D71429F for <gavinpatel@example.net>; Thu, 1 Feb 2007 02:46:05 -0800 (PST) Message-ID: <6307893.1170326765775.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 02:46:05 -0800 (PST) From: "Knut Anders Hatlen (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Commented: (DERBY-2191) Cleanup of FormatableBitSet In-Reply-To: <4003790.1166447903211.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469402 ] Knut Anders Hatlen commented on DERBY-2191: ------------------------------------------- Thanks Dyre! Committed shrink.v2 with revision 502185. > Cleanup of FormatableBitSet > --------------------------- > > Key: DERBY-2191 > URL: https://issues.apache.org/jira/browse/DERBY-2191 > Project: Derby > Issue Type: Improvement > Components: Miscellaneous > Affects Versions: 83.161.120.155 > Reporter: Dyre Tjeldvoll > Assigned To: Dyre Tjeldvoll > Priority: Trivial > Fix For: 83.161.120.155 > > Attachments: anysetbit.v1.diff, anysetbit.v1.stat, anysetbit.v2.diff, bitops.v1.diff, bitops.v1.stat, bitops.v2.diff, bitops.v2.stat, bitops.v3.diff, bitopt.v1.diff, bitopt.v1.stat, bitopt.v2.diff, boundarycheck.v1.diff, boundarycheck.v1.stat, cleanup2191.diff, cleanup2191.stat, deadcode.v1.diff, deadcode.v2.diff, fbstst.v1.diff, fbstst.v1.stat, FormatableBitSetTest.java, numbitsset.v1.diff, numbitsset.v1.stat, numbitsset.v2.diff, numbitstest.diff, shrink.v1.diff, shrink.v1.stat, shrink.v2.diff, unusedmethods.v1.diff, unusedmethods.v1.stat, valuenotnull.v1.diff, valuenotnull.v1.stat > > > The implementation of FormatableBitSet could be streamlined. Dead code can be removed and the implementation of some methods can be simplified. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 13:59:39 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 42893 invoked from network); 1 Feb 2007 13:59:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 13:59:28 -0000 Received: (qmail 8515 invoked by uid 500); 1 Feb 2007 13:59:33 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 8423 invoked by uid 500); 1 Feb 2007 13:59:33 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 8373 invoked by uid 99); 1 Feb 2007 13:59:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 05:59:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 05:59:26 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id C4CBA71429F for <gavinpatel@example.net>; Thu, 1 Feb 2007 05:59:05 -0800 (PST) Message-ID: <30669457.1170338345803.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 05:59:05 -0800 (PST) From: "Knut Anders Hatlen (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Commented: (DERBY-2107) Move page latching out of the lock manager In-Reply-To: <5315982.1164184022042.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469431 ] Knut Anders Hatlen commented on DERBY-2107: ------------------------------------------- If there are no more comments, I plan to commit 1c after the weekend. > Move page latching out of the lock manager > ------------------------------------------ > > Key: DERBY-2107 > URL: https://issues.apache.org/jira/browse/DERBY-2107 > Project: Derby > Issue Type: Improvement > Components: Performance, Services, Store > Affects Versions: 83.161.120.155 > Reporter: Knut Anders Hatlen > Assigned To: Knut Anders Hatlen > Priority: Minor > Attachments: derby-2107-1a.diff, derby-2107-1a.stat, derby-2107-1b.diff, derby-2107-1c.diff, derby-2107-1c.stat > > > Latching of pages could be done more efficiently locally in store than in the lock manager. See the discussion here: http://thread.gmane.org/gmane.comp.apache.db.derby.devel/33135 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 14:59:28 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 66038 invoked from network); 1 Feb 2007 14:59:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 14:59:27 -0000 Received: (qmail 28517 invoked by uid 500); 1 Feb 2007 14:59:33 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 28479 invoked by uid 500); 1 Feb 2007 14:59:33 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 28469 invoked by uid 99); 1 Feb 2007 14:59:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 06:59:32 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 06:59:26 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id D494571429F for <gavinpatel@example.net>; Thu, 1 Feb 2007 06:59:05 -0800 (PST) Message-ID: <19746514.1170341945867.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 06:59:05 -0800 (PST) From: "Mamta A. Satoor (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Commented: (DERBY-1275) Provide a way to enable client tracing without changing the application In-Reply-To: <1486602.1146544066463.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469447 ] Mamta A. Satoor commented on DERBY-1275: ---------------------------------------- Dan, I think I understand the Decorator class comment. It seems that the purpose of TestConfiguration class is to have static methods which will do some setup related things and then return an instance of a decorator based on that (eg sqlAuthorizationDecorator() method sets up the sqlAuthorization property and then passes it on to the decorator DatabaseChangeSetup). But the static method I added simply returns an instance of the decorator using the parameters passed to the static method. And hence it doesn't fit the definition of the TestConfiguration class. I will add another class called say, TestDecorator. I will move my following method from TestConfiguration class to the new TestDecorator class. Is this what you were proposing? public static Test systemPropertiesSetupDecorator(Test suite, Properties newProperties) { return new SystemPropertyTestSetup(suite, newProperties); } > Provide a way to enable client tracing without changing the application > ----------------------------------------------------------------------- > > Key: DERBY-1275 > URL: https://issues.apache.org/jira/browse/DERBY-1275 > Project: Derby > Issue Type: Improvement > Components: Network Client > Affects Versions: 83.161.120.155, 83.161.120.155 > Reporter: Kathey Marsden > Assigned To: Mamta A. Satoor > Priority: Minor > Fix For: 83.161.120.155 > > Attachments: DERBY1275EnableClientTracingDiffV1.txt, DERBY1275EnableClientTracingDiffV2.txt, DERBY1275EnableClientTracingDiffV3.txt, DERBY1275EnableClientTracingDiffV4.txt, DERBY1275EnableClientTracingStatV1.txt, DERBY1275EnableClientTracingStatV2.txt, DERBY1275EnableClientTracingStatV3.txt, DERBY1275EnableClientTracingStatV4.txt > > > Currently the client tracing can be enabled by setting attributes on the client url, setXXX methods on the DataSource or calling DriverManager.setLogWriter(), but it often cannot be enabled in a deployed client application because all of these API's require modification of the application or its configuration files. > It would be good to have a global way to turn on client tracing. A system property pointing to a property file is one possibility but probably not ideal because of the impact in class loader contexts. I am not sure what the other possiblities are, -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 15:20:30 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 71779 invoked from network); 1 Feb 2007 15:20:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 15:20:29 -0000 Received: (qmail 66625 invoked by uid 500); 1 Feb 2007 15:20:34 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 66598 invoked by uid 500); 1 Feb 2007 15:20:34 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 66586 invoked by uid 99); 1 Feb 2007 15:20:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 07:20:34 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 07:20:27 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id EA84B7142B6 for <gavinpatel@example.net>; Thu, 1 Feb 2007 07:20:05 -0800 (PST) Message-ID: <30586900.1170343205958.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 07:20:05 -0800 (PST) From: "Daniel John Debrunner (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Commented: (DERBY-1275) Provide a way to enable client tracing without changing the application In-Reply-To: <1486602.1146544066463.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469453 ] Daniel John Debrunner commented on DERBY-1275: ---------------------------------------------- That's the general idea, at least for existing decorators returned by TestConfiguration, but I'm curious as to why you feel in this case the static method is useful or required. A class can be used as a decorator, just using new SystemPropertyTestSetup(suite, newProperties) which is actually less to type than TestDecorator.systemPropertiesSetupDecorator(suite, newProperties) Then exposing the class as the decorator actually allows tests to customize it. Typically a test may want to perform additional setup or teardown based upon an existing decorator. Java allows this without having to define an additional class explicitly. For example see CleanDatabaseTestSetup, which allows a test to use it in-line and easily add DDL statements. This is from the javadoc for CleanDatabaseTestSetup. return new CleanDatabaseTestSetup(suite) { protected void decorateSQL(Statement s) throws SQLException { s.execute("CREATE TABLE T (I INT)"); s.execute("CREATE INDEX TI ON T(I)") } }; If the CleanDatabaseTestSetup was exposed as a static method then this style of customization is no longer possible. Exposing it as a class and a static method has the downside of multiple ways to perform the same task, which tends to make it harder for people to add tests, e.g. which way should I use? > Provide a way to enable client tracing without changing the application > ----------------------------------------------------------------------- > > Key: DERBY-1275 > URL: https://issues.apache.org/jira/browse/DERBY-1275 > Project: Derby > Issue Type: Improvement > Components: Network Client > Affects Versions: 83.161.120.155, 83.161.120.155 > Reporter: Kathey Marsden > Assigned To: Mamta A. Satoor > Priority: Minor > Fix For: 83.161.120.155 > > Attachments: DERBY1275EnableClientTracingDiffV1.txt, DERBY1275EnableClientTracingDiffV2.txt, DERBY1275EnableClientTracingDiffV3.txt, DERBY1275EnableClientTracingDiffV4.txt, DERBY1275EnableClientTracingStatV1.txt, DERBY1275EnableClientTracingStatV2.txt, DERBY1275EnableClientTracingStatV3.txt, DERBY1275EnableClientTracingStatV4.txt > > > Currently the client tracing can be enabled by setting attributes on the client url, setXXX methods on the DataSource or calling DriverManager.setLogWriter(), but it often cannot be enabled in a deployed client application because all of these API's require modification of the application or its configuration files. > It would be good to have a global way to turn on client tracing. A system property pointing to a property file is one possibility but probably not ideal because of the impact in class loader contexts. I am not sure what the other possiblities are, -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 15:39:36 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 79000 invoked from network); 1 Feb 2007 15:39:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 15:39:34 -0000 Received: (qmail 94252 invoked by uid 500); 1 Feb 2007 15:39:36 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 94210 invoked by uid 500); 1 Feb 2007 15:39:35 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 94179 invoked by uid 99); 1 Feb 2007 15:39:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 07:39:35 -0800 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 07:39:28 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 8E9D27142F8 for <gavinpatel@example.net>; Thu, 1 Feb 2007 07:39:07 -0800 (PST) Message-ID: <2010642.1170344347581.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 07:39:07 -0800 (PST) From: gavinpatel@example.net To: gavinpatel@example.net Subject: [jira] Subscription: Derby: JIRA issues with patch available MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Issue Subscription Filter: Derby: JIRA issues with patch available (17 issues) Subscriber: derby-dev Key Summary DERBY-1275 Provide a way to enable client tracing without changing the application https://issues.apache.org/jira/browse/DERBY-1275 DERBY-2107 Move page latching out of the lock manager https://issues.apache.org/jira/browse/DERBY-2107 DERBY-2280 DatabaseMetaData.getTypeInfo() UNSIGNED_ATTRIBUTE and AUTO_INCREMENT column returns incorrect information for BLOB & CLOB data type https://issues.apache.org/jira/browse/DERBY-2280 DERBY-2258 DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly. https://issues.apache.org/jira/browse/DERBY-2258 DERBY-2108 Implement SSL/TLS communication between client and server https://issues.apache.org/jira/browse/DERBY-2108 DERBY-2247 provide set methods for blob in embeded driver https://issues.apache.org/jira/browse/DERBY-2247 DERBY-1662 Document derbyrun.jar https://issues.apache.org/jira/browse/DERBY-1662 DERBY-2087 Clean up of a database server directory after running junit tests. https://issues.apache.org/jira/browse/DERBY-2087 DERBY-1842 Accessibility of figures in Derby Docs https://issues.apache.org/jira/browse/DERBY-1842 DERBY-2137 CALL (PROCEDURE) statement documentation in reference manual has incomplete syntax for arguments https://issues.apache.org/jira/browse/DERBY-2137 DERBY-2031 Convert derbynet/testProtocol.java to JUnit https://issues.apache.org/jira/browse/DERBY-2031 DERBY-2255 ij should indicate that it is waiting for more input in a multi-line interactive statement. https://issues.apache.org/jira/browse/DERBY-2255 DERBY-1620 SQL CASE statement returns ERROR 42X89 when including NULL as a return value https://issues.apache.org/jira/browse/DERBY-1620 DERBY-1909 ALTER TABLE DROP COLUMN needs to update GRANTed column privileges https://issues.apache.org/jira/browse/DERBY-1909 DERBY-2161 MessageBuilder can write the properties file using the wrong encoding. https://issues.apache.org/jira/browse/DERBY-2161 DERBY-681 Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses https://issues.apache.org/jira/browse/DERBY-681 DERBY-1938 Add support for setObject(<arg>, null) https://issues.apache.org/jira/browse/DERBY-1938 From gavinpatel@example.net Thu Feb 01 15:47:35 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 84197 invoked from network); 1 Feb 2007 15:47:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 15:47:30 -0000 Received: (qmail 12305 invoked by uid 500); 1 Feb 2007 15:47:35 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 12264 invoked by uid 500); 1 Feb 2007 15:47:35 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 12209 invoked by uid 99); 1 Feb 2007 15:47:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 07:47:34 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 07:47:26 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 89B1B7142FB for <gavinpatel@example.net>; Thu, 1 Feb 2007 07:47:06 -0800 (PST) Message-ID: <14870363.1170344826561.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 07:47:06 -0800 (PST) From: "Julius Stroffek (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Updated: (DERBY-2087) Clean up of a database server directory after running junit tests. In-Reply-To: <31291217.1163593657045.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julius Stroffek updated DERBY-2087: ----------------------------------- Attachment: d2087_round2.stat d2087_round2.diff > Clean up of a database server directory after running junit tests. > ------------------------------------------------------------------ > > Key: DERBY-2087 > URL: https://issues.apache.org/jira/browse/DERBY-2087 > Project: Derby > Issue Type: Improvement > Components: Test > Affects Versions: 83.161.120.155 > Reporter: Julius Stroffek > Assigned To: Julius Stroffek > Priority: Minor > Fix For: 83.161.120.155 > > Attachments: d2087.diff, d2087.stat, d2087_round2.diff, d2087_round2.stat, d2087_try2.diff, d2087_try2.stat > > > If I create a test using multiple connections using code like this > DataSource ds1 = JDBCDataSource.getDataSource("FIRSTDB1"); > JDBCDataSource.setBeanProperty(ds1, "connectionAttributes", "create=true"); > Connection conn1 = ds1.getConnection(); > the files created on a server does not get cleaned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 16:55:37 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 16775 invoked from network); 1 Feb 2007 16:55:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 16:55:36 -0000 Received: (qmail 53996 invoked by uid 500); 1 Feb 2007 16:55:41 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 53956 invoked by uid 500); 1 Feb 2007 16:55:41 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 53947 invoked by uid 99); 1 Feb 2007 16:55:41 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 08:55:41 -0800 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [83.161.120.155] (HELO brmea-mail-1.sun.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 08:55:30 -0800 Received: from dm-norway-01.uk.sun.com ([83.161.120.155]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l11Gt8Fd015623 for <gavinpatel@example.net>; Thu, 1 Feb 2007 09:55:09 -0700 (MST) Received: from clustra.norway.sun.com (clustra.Norway.Sun.COM [83.161.120.155]) by dm-norway-01.uk.sun.com (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with SMTP id l11Gt7ks000404 for <gavinpatel@example.net>; Thu, 1 Feb 2007 16:55:07 GMT Received: (qmail 14610 invoked from network); 1 Feb 2007 16:55:07 -0000 Received: from khepri31.norway.sun.com (83.161.120.155) by clustra.norway.sun.com with QMQP; 1 Feb 2007 16:55:07 -0000 Date: 1 Feb 2007 16:55:07 -0000 Message-ID: <20070201165507.6599.qmail@khepri31> Subject: Regression Test Report - Daily 501898 - Sun DBTG To: gavinpatel@example.net From: gavinpatel@example.net X-Virus-Checked: Checked by ClamAV on apache.org [Auto-generated mail] *Daily* 501898/2007-01-31 18:00:10 CET Failed Tests OK Skip Duration Suite ------------------------------------------------------- *Jvm: 1.6* lin NA NA NA NA derbyall NA NA NA NA suitesAll sles 0 498 498 0 101.24% derbyall 0 6623 6623 0 116.67% suitesAll sol 0 498 498 0 103.14% derbyall 0 6623 6623 0 152.82% suitesAll solN+1 0 498 498 0 123.35% derbyall 0 6623 6623 0 191.49% suitesAll sparc 0 498 498 0 107.88% derbyall 0 6623 6623 0 178.70% suitesAll win NA NA NA NA derbyall F:2,E:0 6623 6621 0 112.04% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-501898.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/501898.html *Jvm: 1.5* lin 0 492 492 2 97.93% derbyall 0 2374 2374 0 190.30% suitesAll sles 1 492 491 2 102.93% derbyall 0 2374 2374 0 117.56% suitesAll sol 0 492 492 2 107.09% derbyall 0 2374 2374 0 147.79% suitesAll solN+1 0 492 492 2 128.22% derbyall 0 2374 2374 0 152.58% suitesAll sparc 0 492 492 2 108.39% derbyall 0 2374 2374 0 144.18% suitesAll win 0 492 492 2 119.10% derbyall F:2,E:0 2374 2372 0 107.32% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-501898.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/501898.html *Jvm: 1.4* lin 0 486 486 4 98.39% derbyall 0 2370 2370 0 194.26% suitesAll sles 0 486 486 4 100.85% derbyall 0 2370 2370 0 118.38% suitesAll sol 0 486 486 4 103.70% derbyall 0 2370 2370 0 144.11% suitesAll solN+1 0 486 486 4 130.47% derbyall 0 2370 2370 0 164.22% suitesAll sparc 0 486 486 4 109.36% derbyall 0 2370 2370 0 156.20% suitesAll win 0 486 486 4 69.06% derbyall F:2,E:0 2370 2368 0 115.80% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-501898.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/501898.html ------------------------------------------------------- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/501898.txt ( All results in http://dbtg.thresher.com/derby/test/ ) From gavinpatel@example.net Thu Feb 01 17:25:36 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 30194 invoked from network); 1 Feb 2007 17:25:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 17:25:35 -0000 Received: (qmail 9209 invoked by uid 500); 1 Feb 2007 17:25:34 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 9174 invoked by uid 500); 1 Feb 2007 17:25:34 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 9114 invoked by uid 99); 1 Feb 2007 17:25:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 09:25:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 09:25:26 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 7F02E7142D4 for <gavinpatel@example.net>; Thu, 1 Feb 2007 09:25:06 -0800 (PST) Message-ID: <25133978.1170350706517.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 09:25:06 -0800 (PST) From: "Julius Stroffek (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Updated: (DERBY-2087) Clean up of a database server directory after running junit tests. In-Reply-To: <31291217.1163593657045.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julius Stroffek updated DERBY-2087: ----------------------------------- Attachment: d2087_round2_try2.stat d2087_round2_try2.diff I created an additional patch which uses logical database names in additionalDatabaseDecorator function (which replaces singleUseDatabaseDecorator with database name). I added also a openConnection method where one can specify a connection attributes as a string. Since the prototype of new method openConnection(String dbName, String connectionAttributes) added to Connector interface conflicts with the openConnection(String user, String password) and this method is not used I commented it and have a plan to remove it since it is possible to specify user name and password in connection attributes. Is ok to do it this way or it is better to define connection properties in Properties object instead of string? I think that using String for connection attributes is simpler to use. I ran derbyall and suites.All without failures. Please, give me any comments or suggestions. > Clean up of a database server directory after running junit tests. > ------------------------------------------------------------------ > > Key: DERBY-2087 > URL: https://issues.apache.org/jira/browse/DERBY-2087 > Project: Derby > Issue Type: Improvement > Components: Test > Affects Versions: 83.161.120.155 > Reporter: Julius Stroffek > Assigned To: Julius Stroffek > Priority: Minor > Fix For: 83.161.120.155 > > Attachments: d2087.diff, d2087.stat, d2087_round2.diff, d2087_round2.stat, d2087_round2_try2.diff, d2087_round2_try2.stat, d2087_try2.diff, d2087_try2.stat > > > If I create a test using multiple connections using code like this > DataSource ds1 = JDBCDataSource.getDataSource("FIRSTDB1"); > JDBCDataSource.setBeanProperty(ds1, "connectionAttributes", "create=true"); > Connection conn1 = ds1.getConnection(); > the files created on a server does not get cleaned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 17:28:28 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 31770 invoked from network); 1 Feb 2007 17:28:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 17:28:27 -0000 Received: (qmail 14949 invoked by uid 500); 1 Feb 2007 17:28:33 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 14792 invoked by uid 500); 1 Feb 2007 17:28:32 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 14783 invoked by uid 99); 1 Feb 2007 17:28:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 09:28:32 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 09:28:26 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id BD16B71429F for <gavinpatel@example.net>; Thu, 1 Feb 2007 09:28:05 -0800 (PST) Message-ID: <14784714.1170350885772.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 09:28:05 -0800 (PST) From: "Rick Hillegas (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Commented: (DERBY-2252) Add Jar IDs to the EXTERNAL names in routine declarations In-Reply-To: <23860272.1169134650449.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469517 ] Rick Hillegas commented on DERBY-2252: -------------------------------------- Thanks for the feedback, Dan. I have incorporated your improvements in the next revs of this spec and the companion spec for phase 3 (DERBY-2253). I will wait a bit to collect more feedback before posting the new revs. 1) I added signatures to the syntax of the EXTERNAL NAMEs as you suggested. 2) I clarified class/method resolution rules. 3) The System Tables section now explains my reasons for tracking jar IDs in a new SYSALIASES.FILEID column. The issue here was not dependency tracking but rather the construction of the jar-specific classpath. That is addressed in the phase 3 spec but I can see that some explanation is needed in this spec too. I agree that we could reconstruct this information from the dependency system. But I think that modelling the jar ID in SYSALIASES will make it more straightforward to construct the jar-specific classpath and it will make it easier for tech support to figure out that classpath from the catalogs. 4) I have improved the REVOKE USAGE explanation as you suggested. > Add Jar IDs to the EXTERNAL names in routine declarations > --------------------------------------------------------- > > Key: DERBY-2252 > URL: https://issues.apache.org/jira/browse/DERBY-2252 > Project: Derby > Issue Type: New Feature > Components: Security, SQL > Reporter: Rick Hillegas > Attachments: jarIDs.html > > > This is phase (2) of the work described in the master JIRA DERBY-2206, motivated by the wiki page http://wiki.apache.org/db-derby/JavaRoutineSecurity > This task involves adding Jar IDs to the external names in CREATE PROCEDURE and CREATE FUNCTION statements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 17:45:28 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 39161 invoked from network); 1 Feb 2007 17:45:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 17:45:27 -0000 Received: (qmail 50595 invoked by uid 500); 1 Feb 2007 17:45:32 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 50560 invoked by uid 500); 1 Feb 2007 17:45:32 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 50551 invoked by uid 99); 1 Feb 2007 17:45:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 09:45:32 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 09:45:25 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 8BF6671408A for <gavinpatel@example.net>; Thu, 1 Feb 2007 09:45:05 -0800 (PST) Message-ID: <25795664.1170351905541.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 09:45:05 -0800 (PST) From: "Rick Hillegas (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Updated: (DERBY-2264) Restrict shutdown, upgrade, and encryption powers to the database owner In-Reply-To: <21872343.1169502870264.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-2264: --------------------------------- Attachment: dbaPowers.html Attaching rev 2 of the functional spec. This incorporates Dan's suggestion (in a January 26, 2007 comment on DERBY-2206): only enforce these changes if authentication is turned on. > Restrict shutdown, upgrade, and encryption powers to the database owner > ----------------------------------------------------------------------- > > Key: DERBY-2264 > URL: https://issues.apache.org/jira/browse/DERBY-2264 > Project: Derby > Issue Type: New Feature > Components: Security, SQL > Reporter: Rick Hillegas > Attachments: dbaPowers.html, dbaPowers.html > > > This JIRA separates out the database-owner powers from the system privileges in the master security JIRA DERBY-2109. Restrict the following powers to the database owner for the moment: shutdown, upgrade, and encryption. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 17:54:14 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 42666 invoked from network); 1 Feb 2007 17:54:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 17:54:13 -0000 Received: (qmail 72890 invoked by uid 500); 1 Feb 2007 17:54:18 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 72869 invoked by uid 500); 1 Feb 2007 17:54:18 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Delivered-To: moderator for gavinpatel@example.net Received: (qmail 42711 invoked by uid 99); 1 Feb 2007 17:43:02 -0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of gavinpatel@example.net designates 83.161.120.155 as permitted sender) To: gavinpatel@example.net, gavinpatel@example.net Subject: Derby fully sql-2003 compliant? MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005 Message-ID: <gavinpatel@example.net> From: Christian Lang <gavinpatel@example.net> Date: Thu, 1 Feb 2007 12:42:26 -0500 X-MIMETrack: Serialize by Router on D01ML604/01/M/IBM(Build V80_M3_10312006|October 31, 2006) at 02/01/2007 12:42:29, Serialize complete at 02/01/2007 12:42:29 Content-Type: multipart/alternative; boundary="=_alternative 0061454785257275_=" X-Virus-Checked: Checked by ClamAV on apache.org This is a multipart message in MIME format. --=_alternative 0061454785257275_= Content-Type: text/plain; charset="US-ASCII" Hi, I'm trying to understand which SQL language subset Derby is using. I installed version 83.161.120.155 and tried to compile and execute the following statement: SELECT MIN(A) OVER (PARTITION BY B) FROM C; (which seems a legal SQL-2003 statement). However, the Derby sql compiler complains about the '(' after the 'OVER' keyword. I looked into the sqlgrammar.jj file and could not find a "partition" or "over" gavinpatel@example.net. Is this not supported (yet)? Or am I doing something wrong? Thanks for clarifying, Christian --=_alternative 0061454785257275_= Content-Type: text/html; charset="US-ASCII" <br><font size=2 face="sans-serif">Hi,</font> <br> <br><font size=2 face="sans-serif">I'm trying to understand which SQL language subset Derby is using. I installed version 83.161.120.155 and tried to compile and execute the following statement:</font> <br> <br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; SELECT MIN(A) OVER (PARTITION BY B) FROM C;</font> <br> <br><font size=2 face="sans-serif">(which seems a legal SQL-2003 statement). However, the Derby sql compiler complains about the '(' after the 'OVER' keyword.</font> <br><font size=2 face="sans-serif">I looked into the sqlgrammar.jj file and could not find a &quot;partition&quot; or &quot;over&quot; gavinpatel@example.net. Is this not supported (yet)?</font> <br><font size=2 face="sans-serif">Or am I doing something wrong?</font> <br> <br><font size=2 face="sans-serif">Thanks for clarifying,</font> <br><font size=2 face="sans-serif">Christian</font> <br> --=_alternative 0061454785257275_=-- From gavinpatel@example.net Thu Feb 01 18:05:42 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 47780 invoked from network); 1 Feb 2007 18:05:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 18:05:36 -0000 Received: (qmail 93615 invoked by uid 500); 1 Feb 2007 18:05:42 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 93584 invoked by uid 500); 1 Feb 2007 18:05:42 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 93575 invoked by uid 99); 1 Feb 2007 18:05:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:05:42 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:05:35 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 954477141A3 for <gavinpatel@example.net>; Thu, 1 Feb 2007 10:05:13 -0800 (PST) Message-ID: <976140.1170353113608.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 10:05:13 -0800 (PST) From: "Mamta A. Satoor (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Commented: (DERBY-1275) Provide a way to enable client tracing without changing the application In-Reply-To: <1486602.1146544066463.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469528 ] Mamta A. Satoor commented on DERBY-1275: ---------------------------------------- I think I misunderstood your following comment on Jan 27th to the review package DERBY1275EnableClientTracingDiffV2.txt "The test breaks the pattern for JUnit tests in a few ways: the suite method performs test setup. The suite method is for providing a set of fixtures to run. Setup should be performed in a test decorator for a set of fixtures or the setUp method for each fixture. " I took the above comment to mean that Junit pattern discourages following setup code in the suite() method Properties traceRelatedProperties = new Properties(); traceRelatedProperties.setProperty("derby.client.traceLevel", "64"); traceDirectory = "." + File.separator + "TraceDir" + File.separator; traceRelatedProperties.setProperty("derby.client.traceDirectory", traceDirectory); return new SystemPropertyTestSetup(suite, traceRelatedProperties); Now, I think your comment was really for following piece of code in the suite() method and not for the code related to SystemPropertyTestSetup fixture. + File dir = new File( traceDirectory ); + dir.mkdirs(); This is the only outstanding issue that I need to resolve on this Jira entry based on all different comments. I have already moved the directory setup code in the setUp() method in the .DERBY1275EnableClientTracingDiffV4.txt Next, I will remove systemPropertiesSetupDecorator from TestConfiguration and have my junit test directly use the fixture SystemPropertyTestSetup. > Provide a way to enable client tracing without changing the application > ----------------------------------------------------------------------- > > Key: DERBY-1275 > URL: https://issues.apache.org/jira/browse/DERBY-1275 > Project: Derby > Issue Type: Improvement > Components: Network Client > Affects Versions: 83.161.120.155, 83.161.120.155 > Reporter: Kathey Marsden > Assigned To: Mamta A. Satoor > Priority: Minor > Fix For: 83.161.120.155 > > Attachments: DERBY1275EnableClientTracingDiffV1.txt, DERBY1275EnableClientTracingDiffV2.txt, DERBY1275EnableClientTracingDiffV3.txt, DERBY1275EnableClientTracingDiffV4.txt, DERBY1275EnableClientTracingStatV1.txt, DERBY1275EnableClientTracingStatV2.txt, DERBY1275EnableClientTracingStatV3.txt, DERBY1275EnableClientTracingStatV4.txt > > > Currently the client tracing can be enabled by setting attributes on the client url, setXXX methods on the DataSource or calling DriverManager.setLogWriter(), but it often cannot be enabled in a deployed client application because all of these API's require modification of the application or its configuration files. > It would be good to have a global way to turn on client tracing. A system property pointing to a property file is one possibility but probably not ideal because of the impact in class loader contexts. I am not sure what the other possiblities are, -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 18:15:50 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 50333 invoked from network); 1 Feb 2007 18:15:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 18:15:48 -0000 Received: (qmail 10975 invoked by uid 500); 1 Feb 2007 18:15:52 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 10943 invoked by uid 500); 1 Feb 2007 18:15:52 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 10924 invoked by uid 99); 1 Feb 2007 18:15:52 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:15:52 -0800 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [83.161.120.155] (HELO gmp-ea-fw-1.sun.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:15:42 -0800 Received: from d1-emea-09.sun.com (d1-emea-09.sun.com [83.161.120.155]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l11IFJ4W001715; Thu, 1 Feb 2007 18:15:20 GMT Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <gavinpatel@example.net> (original mail from gavinpatel@example.net); Thu, 01 Feb 2007 18:15:19 +0000 (GMT) Received: from khepri29.sun.com ([83.161.120.155]) by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <gavinpatel@example.net>; Thu, 01 Feb 2007 18:15:19 +0000 (GMT) Date: Thu, 01 Feb 2007 19:15:16 +0100 From: gavinpatel@example.net Subject: Re: Derby fully sql-2003 compliant? In-reply-to: <gavinpatel@example.net> Sender: gavinpatel@example.net To: Derby Discussion <gavinpatel@example.net> Cc: gavinpatel@example.net Message-id: <gavinpatel@example.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT References: <gavinpatel@example.net> User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (usg-unix-v) X-Virus-Checked: Checked by ClamAV on apache.org Christian Lang <gavinpatel@example.net> writes: > Hi, > > I'm trying to understand which SQL language subset Derby is using. I > installed version 83.161.120.155 and tried to compile and execute the following > statement: > > SELECT MIN(A) OVER (PARTITION BY B) FROM C; > > (which seems a legal SQL-2003 statement). However, the Derby sql compiler > complains about the '(' after the 'OVER' keyword. > I looked into the sqlgrammar.jj file and could not find a "partition" or > "over" gavinpatel@example.net. Is this not supported (yet)? > Or am I doing something wrong? I don't find anything about this on http://wiki.apache.org/db-derby/SQLvsDerbyFeatures so either it is completely over-looked, or it isn't required. -- dt From gavinpatel@example.net Thu Feb 01 18:43:33 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 59008 invoked from network); 1 Feb 2007 18:43:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 18:43:29 -0000 Received: (qmail 57240 invoked by uid 500); 1 Feb 2007 18:43:34 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 57213 invoked by uid 500); 1 Feb 2007 18:43:34 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 57171 invoked by uid 99); 1 Feb 2007 18:43:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:43:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:43:26 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 481877142E2 for <gavinpatel@example.net>; Thu, 1 Feb 2007 10:43:06 -0800 (PST) Message-ID: <20479227.1170355386293.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 10:43:06 -0800 (PST) From: "Rick Hillegas (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Assigned: (DERBY-2196) Run standalone network server with security manager by default In-Reply-To: <4216116.1166553920991.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas reassigned DERBY-2196: ------------------------------------ Assignee: Rick Hillegas > Run standalone network server with security manager by default > -------------------------------------------------------------- > > Key: DERBY-2196 > URL: https://issues.apache.org/jira/browse/DERBY-2196 > Project: Derby > Issue Type: Improvement > Components: Network Server, Security > Reporter: Daniel John Debrunner > Assigned To: Rick Hillegas > Attachments: secureServer.html, secureServer.html, secureServer.html, secureServer.html > > > From an e-mail discussion: > ... Derby should match the security provided by typical client server systems such as DB2, Oracle, etc. I > think in this case system/database owners are trusting the database > system to ensure that their system cannot be attacked. So maybe if Derby > is booted as a standalone server with no security manager involved, it > should install one with a default security policy. Thus allowing Derby > to use Java security manager to manage system privileges but not > requiring everyone to become familiar with them. > http://mail-archives.gavinpatel@example.net%3e > I imagine such a policy would allow any access to databases under derby.system.home and/or user.home. > By standalone I mean the network server was started though the main() method (command line). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 18:43:35 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 58975 invoked from network); 1 Feb 2007 18:43:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 18:43:28 -0000 Received: (qmail 57190 invoked by uid 500); 1 Feb 2007 18:43:34 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 57163 invoked by uid 500); 1 Feb 2007 18:43:33 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 57145 invoked by uid 99); 1 Feb 2007 18:43:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:43:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:43:26 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 1C6487142D0 for <gavinpatel@example.net>; Thu, 1 Feb 2007 10:43:06 -0800 (PST) Message-ID: <6118530.1170355386114.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 10:43:06 -0800 (PST) From: "Dag H. Wanvik (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Commented: (DERBY-2207) Improve usability of Derby's client/server security by implementing ANSI Roles In-Reply-To: <3404894.1167844227677.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469543 ] Dag H. Wanvik commented on DERBY-2207: -------------------------------------- I have made a Wiki page for this topic and added some thoughts from a preliminary investigation. Please see: http://wiki.apache.org/db-derby/SqlRoles > Improve usability of Derby's client/server security by implementing ANSI Roles > ------------------------------------------------------------------------------ > > Key: DERBY-2207 > URL: https://issues.apache.org/jira/browse/DERBY-2207 > Project: Derby > Issue Type: New Feature > Components: Security, SQL > Reporter: Rick Hillegas > > Implementing ANSI Roles will make it easier to manage security for multi-user applications with high user turnover. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 18:46:05 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 61143 invoked from network); 1 Feb 2007 18:46:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 18:46:03 -0000 Received: (qmail 62437 invoked by uid 500); 1 Feb 2007 18:46:02 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 62406 invoked by uid 500); 1 Feb 2007 18:46:02 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 62387 invoked by uid 99); 1 Feb 2007 18:46:02 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:46:02 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [83.161.120.155] (HELO gmp-ea-fw-1.sun.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:45:52 -0800 Received: from d1-emea-09.sun.com ([83.161.120.155]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l11IjTC6026408; Thu, 1 Feb 2007 18:45:30 GMT Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <gavinpatel@example.net> (original mail from gavinpatel@example.net); Thu, 01 Feb 2007 18:45:29 +0000 (GMT) Received: from localhost (84.84-48-48.nextgentel.com [83.161.120.155]) by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <gavinpatel@example.net>; Thu, 01 Feb 2007 18:45:29 +0000 (GMT) Date: Thu, 01 Feb 2007 19:45:26 +0100 From: "Bernt M. Johnsen" <gavinpatel@example.net> Subject: Re: Derby fully sql-2003 compliant? In-reply-to: <gavinpatel@example.net> Sender: gavinpatel@example.net To: gavinpatel@example.net Cc: Derby Discussion <gavinpatel@example.net> Message-id: <gavinpatel@example.net> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/signed; boundary=IJpNTDwzlM2Ie8A6; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline References: <gavinpatel@example.net> <gavinpatel@example.net> User-Agent: Mutt/1.5.9i X-Virus-Checked: Checked by ClamAV on apache.org --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable >>>>>>>>>>>> gavinpatel@example.net wrote (2007-02-01 19:15:16): > Christian Lang <gavinpatel@example.net> writes: >=20 > > Hi, > > > > I'm trying to understand which SQL language subset Derby is using. I=20 > > installed version 83.161.120.155 and tried to compile and execute the followi= ng=20 > > statement: > > > > SELECT MIN(A) OVER (PARTITION BY B) FROM C; > > > > (which seems a legal SQL-2003 statement). However, the Derby sql compil= er=20 > > complains about the '(' after the 'OVER' keyword. > > I looked into the sqlgrammar.jj file and could not find a "partition" o= r=20 > > "over" gavinpatel@example.net. Is this not supported (yet)? > > Or am I doing something wrong? >=20 > I don't find anything about this on > http://wiki.apache.org/db-derby/SQLvsDerbyFeatures >=20 > so either it is completely over-looked, or it isn't required. It is in section 7.11 <window clause> in the 2003 standard Tis is optional feature "T612 Advanced OLAP operations" which is not implemented in Derby --=20 Bernt Marius Johnsen, Database Technology Group,=20 Staff Engineer, Technical Lead Derby/Java DB Sun Microsystems, Trondheim, Norway --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFFwjVGlFBD9TXBAPARAhwFAJ9lPFShbnLJHJP6hM4jcM5Yg53DEACgxOE3 sCIKPCHx0NTZcOGmnEmF0rY= =3GuP -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6-- From gavinpatel@example.net Thu Feb 01 18:47:27 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 61896 invoked from network); 1 Feb 2007 18:47:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 18:47:27 -0000 Received: (qmail 67439 invoked by uid 500); 1 Feb 2007 18:47:33 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 67228 invoked by uid 500); 1 Feb 2007 18:47:32 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 67219 invoked by uid 99); 1 Feb 2007 18:47:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:47:32 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:47:25 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id 8BFE571408A for <gavinpatel@example.net>; Thu, 1 Feb 2007 10:47:05 -0800 (PST) Message-ID: <864230.1170355625536.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 10:47:05 -0800 (PST) From: "Daniel John Debrunner (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Commented: (DERBY-2252) Add Jar IDs to the EXTERNAL names in routine declarations In-Reply-To: <23860272.1169134650449.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469544 ] Daniel John Debrunner commented on DERBY-2252: ---------------------------------------------- Thanks for putting up with all my comments Rick. > 3) The System Tables section now explains my reasons for tracking jar IDs in a new SYSALIASES.FILEID column. The issue here was not dependency tracking but rather the construction of the jar-specific classpath. I look forward to seeing that, I don't see how the definition of an entry point is related to the jar specific class path, but I haven't thought a lot about how to implement it. > Add Jar IDs to the EXTERNAL names in routine declarations > --------------------------------------------------------- > > Key: DERBY-2252 > URL: https://issues.apache.org/jira/browse/DERBY-2252 > Project: Derby > Issue Type: New Feature > Components: Security, SQL > Reporter: Rick Hillegas > Attachments: jarIDs.html > > > This is phase (2) of the work described in the master JIRA DERBY-2206, motivated by the wiki page http://wiki.apache.org/db-derby/JavaRoutineSecurity > This task involves adding Jar IDs to the external names in CREATE PROCEDURE and CREATE FUNCTION statements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 18:47:30 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 61963 invoked from network); 1 Feb 2007 18:47:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 18:47:28 -0000 Received: (qmail 67496 invoked by uid 500); 1 Feb 2007 18:47:33 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 67458 invoked by uid 500); 1 Feb 2007 18:47:33 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 67433 invoked by uid 99); 1 Feb 2007 18:47:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:47:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2007 10:47:25 -0800 Received: from brutus (localhost [83.161.120.155]) by brutus.apache.org (Postfix) with ESMTP id C62FC71429F for <gavinpatel@example.net>; Thu, 1 Feb 2007 10:47:05 -0800 (PST) Message-ID: <28836057.1170355625809.JavaMail.jira@brutus> Date: Thu, 1 Feb 2007 10:47:05 -0800 (PST) From: "A B (JIRA)" <gavinpatel@example.net> To: gavinpatel@example.net Subject: [jira] Created: (DERBY-2282) Incorrect "transitive closure" logic leads to inconsistent behavior for binary comparison predicates. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Incorrect "transitive closure" logic leads to inconsistent behavior for binary comparison predicates. ----------------------------------------------------------------------------------------------------- Key: DERBY-2282 URL: https://issues.apache.org/jira/browse/DERBY-2282 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 83.161.120.155, 83.161.120.155, 83.161.120.155, 83.161.120.155, 83.161.120.155, 83.161.120.155, 83.161.120.155, 83.161.120.155, 83.161.120.155, 83.161.120.155, 83.161.120.155, 83.161.120.155, 83.161.120.155 Reporter: A B Priority: Minor The logic that handles "transive closure" for search predicates is in the "searchClauseTransitiveClosure()" method of impl/sql/compile/PredicateList.java. That method contains the following logic: else if (operator instanceof BinaryComparisonOperatorNode) { BinaryComparisonOperatorNode bcon = (BinaryComparisonOperatorNode) operator; ValueNode left = bcon.getLeftOperand(); ValueNode right = bcon.getRightOperand(); // RESOLVE: Consider using variant type of the expression, instead of // ConstantNode or ParameterNode in the future. if (left instanceof ColumnReference && (right instanceof ConstantNode || right instanceof ParameterNode)) { searchClauses.addElement(predicate); } else if (right instanceof ConstantNode && left instanceof ColumnReference) { // put the ColumnReference on the left to simplify things bcon.swapOperands(); searchClauses.addElement(predicate); } continue; } Notice that the inner "else-if" condition is wrong. It's supposed to be checking to see if the right node is a ColumnReference and the left node is a Constant, but that's not what it does--instead, it does a check that is really a sub-condition of the "if" condition--i.e. whenever the "else if" condition is true the "if" condition will be true and thus we won't ever execute the "else if" branch. I confirmed this by looking at the code coverage results for 10.2: http://people.apache.org/~fuzzylogic/codecoverage/428586/_files/2f4.html#2d The lines in question are never executed. What this means is that a query which specifies constants on the *left* side of a comparison predicate will behave differently than a query which specifies constants on the *right* side of the same comparison. As an example: create table t1 (i int); create table t2 (j int); insert into t1 values 1, 5, 7, 11, 13, 17, 19; insert into t2 values 23, 29, 31, 37, 43, 47, 53; insert into t1 select 23 * i from t1 where i < 19; insert into t2 select 23 * j from t2 where j < 55; -- Following will show two qualifiers for T2 and three for T1 -- because transitive closure adds two new qualifiers, "t2.j >= 23" -- and "t1.i <= 30" to the list. select * from t1, t2 where t1.i = t2.j and t1.i >= 23 and t2.j <= 30; -- But if we put the constants on the left-hand side, we don't -- detect the transitive closure and thus we have a single qualifier -- for T2 and only two qualifiers for T1. select * from t1, t2 where t1.i = t2.j and 23 <= t1.i and 30 >= t2.j; The above two queries should in theory show the same query plan--but if we execute the above statements while logging query plans, we'll see a difference (as explained in the sql comments above). I did a quick scan of the various branches and found that this incorrect logic appears in every branch back to 10.0 (hence the massive "Affects Versions" list). That said, the result of this bug isn't an error nor is it wrong results, so I'm just marking it "Minor". The fix looks to be pretty straightforward.... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. From gavinpatel@example.net Thu Feb 01 19:24:15 2007 Return-Path: <gavinpatel@example.net> Delivered-To: gavinpatel@example.net Received: (qmail 80499 invoked from network); 1 Feb 2007 19:24:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Feb 2007 19:24:12 -0000 Received: (qmail 53343 invoked by uid 500); 1 Feb 2007 19:24:05 -0000 Delivered-To: gavinpatel@example.net Received: (qmail 53264 invoked by uid 500); 1 Feb 2007 19:24:05 -0000 Mailing-List: contact gavinpatel@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:gavinpatel@example.net> List-Unsubscribe: <mailto:gavinpatel@example.net> List-Post: <mailto:gavinpatel@example.net> List-Id: <derby-dev.db.apache.org> Reply-To: <gavinpatel@example.net> Delivered-To: mailing list gavinpatel@example.net Received: (qmail 53084 invoked by uid 99); 1 Feb 2007 19:24:04 -0000 Received: from herse.apache.org (HELO
{'source': 'Apache Software Foundation Public Mail Archives'}