Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 41736 invoked from network); 7 Jun 2010 17:52:03 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Jun 2010 17:52:03 -0000 Received: (qmail 96106 invoked by uid 500); 7 Jun 2010 17:52:02 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 96081 invoked by uid 500); 7 Jun 2010 17:52:02 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 96074 invoked by uid 99); 7 Jun 2010 17:52:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jun 2010 17:52:02 +0000 X-ASF-Spam-Status: No, hits=-1503.3 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jun 2010 17:52:02 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o57Hpf5Y015433 for ; Mon, 7 Jun 2010 17:51:41 GMT Message-ID: <1557732.5921275933101467.JavaMail.jira@thor> Date: Mon, 7 Jun 2010 13:51:41 -0400 (EDT) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Resolved: (DERBY-4583) TRUE by itself is not accepted in WHERE In-Reply-To: <592118954.267431268667147272.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas resolved DERBY-4583. ---------------------------------- Issue & fix info: (was: [Patch Available]) Resolution: Fixed Committed derby-4583-01-ad-booleanLiterals.diff at subversion revision 952348. The tests ran cleanly for me except for the following error in NetworkServerMBeanTest. The test passed when I re-ran it standalone. I believe that the error is a timing-related heisenbug in that test and is not related to the changes in this patch. There was 1 error: 1) testAttributeAccumulatedConnectionCount(org.apache.derbyTesting.functionTests.tests.management.NetworkServerMBeanTest)java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: org.apache.derby:type=NetworkServer,system=c013800d-0129-1374-c722-ffffe1d7aa3e at java.security.AccessController.doPrivileged(Native Method) at org.apache.derbyTesting.functionTests.tests.management.MBeanTest.getAttribute(MBeanTest.java:379) at org.apache.derbyTesting.functionTests.tests.management.NetworkServerMBeanTest.testAttributeAccumulatedConnectionCount(NetworkServerMBeanTest.java:93) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57) Caused by: javax.management.InstanceNotFoundException: org.apache.derby:type=NetworkServer,system=c013800d-0129-1374-c722-ffffe1d7aa3e at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:627) at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:659) at org.apache.derbyTesting.functionTests.tests.management.MBeanTest$4.run(MBeanTest.java:382) ... 41 more > TRUE by itself is not accepted in WHERE > --------------------------------------- > > Key: DERBY-4583 > URL: https://issues.apache.org/jira/browse/DERBY-4583 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.5.3.0 > Environment: n/a > Reporter: Wouter > Assignee: Rick Hillegas > Attachments: derby-4583-01-ac-booleanLiterals.diff, derby-4583-01-ad-booleanLiterals.diff > > > A SELECT query with a literal boolean value in its WHERE clause results in a syntax error. > How to reproduce: > CREATE TABLE list (value VARCHAR(10)); > Given this table, the following queries result in a syntax error. > SELECT * FROM list WHERE TRUE; > SELECT * FROM list WHERE FALSE; > SELECT * FROM list WHERE value='A' OR TRUE; > Why is TRUE/FALSE not a boolean expression? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.