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 D57D832BEC5 for ; Fri, 15 Oct 2004 17:21:46 +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 80872-06 for ; Fri, 15 Oct 2004 16:21:41 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id C23A632A590 for ; Fri, 15 Oct 2004 17:21:40 +0100 (BST) Received: from [63.195.55.98] (account josh@agliodbs.com HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6507261; Fri, 15 Oct 2004 09:23:03 -0700 From: Josh Berkus Organization: Aglio Database Solutions To: Peter Eisentraut Subject: Re: Some developer FAQ links need updating Date: Fri, 15 Oct 2004 09:19:46 -0700 User-Agent: KMail/1.6.2 Cc: Bruce Momjian , "Joshua D. Drake" , Troels Arvin , pgsql-docs@postgresql.org References: <200410150324.i9F3Owt21113@candle.pha.pa.us> <200410151409.32652.peter_e@gmx.net> In-Reply-To: <200410151409.32652.peter_e@gmx.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410150919.46546.josh@agliodbs.com> 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/38 X-Sequence-Number: 2607 Peter, Folks: > Since we have limited resources, I think it's OK that we concentrate on > working with the latest official standards version. And because the latest > standards version is modularized and has individual feature lists and > packages, it would be a lot easier for us to look good, and it would be > more useful for users to, say, specify a workable set of requirements for > their applications. FWIW, there's two standards that application developers are concerned with as far as I can tell: SQL92, which is the "stable" standard that ensures cross-database compatibility (as well as the only standard that is readable) and SQL2003, which is the current standard and ensures buzzowrd-compliance as well as future prospects. -- Josh Berkus Aglio Database Solutions San Francisco