X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 109D132A06E for ; Thu, 21 Oct 2004 13:21:07 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 92178-04 for ; Thu, 21 Oct 2004 12:20:58 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by svr1.postgresql.org (Postfix) with SMTP id D759C32A002 for ; Thu, 21 Oct 2004 13:20:56 +0100 (BST) Received: (qmail 24389 invoked by uid 65534); 21 Oct 2004 12:20:55 -0000 Received: from dsl-082-082-239-146.arcor-ip.net (EHLO colt.pezone.net) (82.82.239.146) by mail.gmx.net (mp026) with SMTP; 21 Oct 2004 14:20:55 +0200 X-Authenticated: #495269 From: Peter Eisentraut To: Troels Arvin , pgsql-docs@postgresql.org Subject: Re: SQL 2003 conformance Date: Thu, 21 Oct 2004 14:20:49 +0200 User-Agent: KMail/1.5.1 References: <200410121952.24859.peter_e@gmx.net> <200410192306.07434.peter_e@gmx.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410211420.49940.peter_e@gmx.net> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/53 X-Sequence-Number: 2622 Troels Arvin wrote: > An obvious question is how strict to be: Very strict. SQL is a standard, not a guideline. If you can't type in what it says, then it's not supported. We make occasional exceptions in extreme cases. For example, we claim to support aliases in the select list (E051-05), but we require the AS. It would be unhelpful if we instead wrote that we don't support select list aliases. But a comment should be added in these cases. The other exception is that because of additional features that PostgreSQL provides, some standard features may be restricted. Additional reserved key words are an obvious example. But that is allowed by the SQL standard. -- Peter Eisentraut http://developer.postgresql.org/~petere/