Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA16306 for ; Wed, 28 Jul 1999 13:49:13 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id NAA10971; Wed, 28 Jul 1999 13:47:23 -0400 (EDT) To: Thomas Lockhart cc: Drew Whittle , pgsql-sql@postgreSQL.org Subject: Re: [SQL] WHERE parent IN (0,-1) In-reply-to: Your message of Wed, 28 Jul 1999 14:47:43 +0000 <379F180F.F96796FB@alumni.caltech.edu> Date: Wed, 28 Jul 1999 13:47:23 -0400 Message-ID: <10969.933184043@sss.pgh.pa.us> From: Tom Lane >> It's a grammar problem. in_expr_nodes and not_in_expr_nodes expect >> the elements of the IN-list to be AexprConst ... I wonder why not >> a_expr instead? Might be a reduce conflict, but I bet we could at >> least use b_expr. Thomas, any comments? Indeed, there is no reduce conflict created by using a_expr, so I went ahead and committed it. Also tidied the list-generating code a bit. Stuff like select * from int4_tbl where f1 not in (0,123455+1); seems to work fine now. Drew, if you don't want to wait around for 6.6 to fix this, you should be able to just change the occurrences of AexprConst to a_expr in the productions for in_expr_nodes: and not_in_expr_nodes: in src/backend/parser/gram.y. I wouldn't advise trying to copy the current gram.y into 6.5, since there are a bunch of other changes in it already... regards, tom lane