X-Original-To: pgsql-hackers@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C1692475A80 for ; Tue, 15 Apr 2003 10:17:28 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 03C81474E44 for ; Tue, 15 Apr 2003 10:17:28 -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 h3FEHRU6007809; Tue, 15 Apr 2003 10:17:27 -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 "Tue, 15 Apr 2003 15:24:11 +0200" Date: Tue, 15 Apr 2003 10:17:27 -0400 Message-ID: <7808.1050416247@sss.pgh.pa.us> From: Tom Lane X-Spam-Status: No, hits=-29.3 required=5.0 tests=BAYES_01,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/496 X-Sequence-Number: 37986 Peter Eisentraut writes: > That seems like a rather poor excuse for not supporting a standard feature > that people seem to ask about every week. Actually, that was the first complaint that I can recall hearing in quite some time. I think this is simply a place where the spec got it wrong, and we should agree to disagree, as we have done with identifier case-folding for example ... regards, tom lane