X-Original-To: pgsql-hackers@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 05467475B99 for ; Wed, 16 Apr 2003 10:16:51 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 3E464475AE5 for ; Wed, 16 Apr 2003 10:16:50 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h3GEGoU6017739; Wed, 16 Apr 2003 10:16:50 -0400 (EDT) To: Peter Eisentraut Cc: milimeter@163.com, PostgreSQL Development Subject: Re: [GENERAL] Problem about pgsql's column alias In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Wed, 16 Apr 2003 15:46:36 +0200" Date: Wed, 16 Apr 2003 10:16:49 -0400 Message-ID: <17738.1050502609@sss.pgh.pa.us> From: Tom Lane X-Spam-Status: No, hits=-29.1 required=5.0 tests=BAYES_00,EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES, REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/583 X-Sequence-Number: 38073 Peter Eisentraut writes: > Allowing column aliases without AS would break nothing. ... except postfix operators, and whatever else happens to get caught in the crossfire. And we'll still get complaints because it only works for identifiers, not for keywords. Now I'll admit that the postfix-operator issue is probably a red herring, since "SELECT a + b, ..." should get interpreted as infix + in any case. But I think there are other side-effects we have not fully analyzed yet. The one-line grammar hack was not intended to be actually applied, right? Let's see a complete proposal. regards, tom lane