Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 5B6962E0128 for ; Thu, 10 Jan 2008 03:10:41 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 68271-02 for ; Thu, 10 Jan 2008 03:10:36 -0400 (AST) Received: from www01.kensystem.com (www01.kensystem.com [72.19.170.120]) by postgresql.org (Postfix) with ESMTP id DA6792E3871 for ; Thu, 10 Jan 2008 03:10:37 -0400 (AST) Received: from 192.168.0.3 by www01.kensystem.com (SMTPD); id s20080110001035.45277; Thu, 10 Jan 2008 00:10:35 Message-ID: <4785C50F.6010505@kensystem.com> Date: Thu, 10 Jan 2008 00:11:11 -0700 From: Ken Johanson User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Shorthand column labels (SELECT col1 foo, ...) vs (SELECT col1 AS foo, ...) Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/62 X-Sequence-Number: 29915 I notice PG doesn't allow shorthand column labels -- it requires the 'AS' operand. SELECT col1 foo, ...; -> ERROR: syntax error at or near "foo" For compatibility with other databases, what objections might be argued in allowing this syntax in the future? On the 'pros' side I think it eases migration to PG, shortens code, is similar syntax to shorthand table aliases, and some users might argue it has become defacto syntax among DBs. Regards, Ken