Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0DD8E200CAD for ; Wed, 28 Jun 2017 16:07:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0C545160BF7; Wed, 28 Jun 2017 14:07:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 52204160BE8 for ; Wed, 28 Jun 2017 16:07:09 +0200 (CEST) Received: (qmail 22831 invoked by uid 500); 28 Jun 2017 14:07:08 -0000 Mailing-List: contact notifications-help@asterixdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@asterixdb.apache.org Delivered-To: mailing list notifications@asterixdb.apache.org Received: (qmail 22822 invoked by uid 99); 28 Jun 2017 14:07:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jun 2017 14:07:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 321271802CA for ; Wed, 28 Jun 2017 14:07:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id cA7e9fMa51PQ for ; Wed, 28 Jun 2017 14:07:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id B6F806106C for ; Wed, 28 Jun 2017 14:07:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B54D5E0DA1 for ; Wed, 28 Jun 2017 14:07:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6741E241BD for ; Wed, 28 Jun 2017 14:07:00 +0000 (UTC) Date: Wed, 28 Jun 2017 14:07:00 +0000 (UTC) From: "Michael J. Carey (JIRA)" To: notifications@asterixdb.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ASTERIXDB-1960) Possible error in SQL++ boolean WHERE handling? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 28 Jun 2017 14:07:10 -0000 [ https://issues.apache.org/jira/browse/ASTERIXDB-1960?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael J. Carey updated ASTERIXDB-1960: ---------------------------------------- Component/s: SQL - Translator SQL++ *DB - AsterixDB > Possible error in SQL++ boolean WHERE handling? > ----------------------------------------------- > > Key: ASTERIXDB-1960 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-1960 > Project: Apache AsterixDB > Issue Type: Bug > Components: *DB - AsterixDB, SQL - Translator SQL++ > Environment: Current *DB master (SQL++) > Reporter: Michael J. Carey > Assignee: Yingyi Bu > > I'm wondering if: > SELECT VALUE user > FROM GleambookUsers user > WHERE user.userSince; > should work as a lazy shorthand for: > SELECT VALUE user > FROM GleambookUsers user > WHERE user.userSince =3D TRUE; > Because if it should, it doesn=E2=80=99t, in current *DB. > The first form yields a runtime error: > "Runtime error: the select condition should be of the boolean type! [Ille= galStateException]" > The fact that it gets this far syntactically suggests that maybe it's ind= eed a bug? -- This message was sent by Atlassian JIRA (v6.4.14#64029)