Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 259E247641A for ; Wed, 28 Aug 2002 16:58:00 -0400 (EDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by postgresql.org (Postfix) with SMTP id 18587475EF7 for ; Wed, 28 Aug 2002 16:57:59 -0400 (EDT) Received: (qmail 9420 invoked by uid 0); 28 Aug 2002 20:57:59 -0000 Received: from pd902f092.dip0.t-ipconnect.de (217.2.240.146) by mail.gmx.net (mp003-rz3) with SMTP; 28 Aug 2002 20:57:59 -0000 Date: Wed, 28 Aug 2002 23:01:25 +0200 (CEST) From: Peter Eisentraut X-X-Sender: peter@localhost.localdomain To: Bruce Momjian Cc: Rod Taylor , Robert Treat , Tom Lane , Larry Rosenman , PostgreSQL-development Subject: Re: [SQL] LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1? In-Reply-To: <200208281438.g7SEcw515550@candle.pha.pa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/2077 X-Sequence-Number: 27760 Bruce Momjian writes: > That SELECT syntax is already too confusing. I don't want to add an > additional documentation specification that provides no value to users. The value of the documentation, especially the reference manual, is that it provides an authorative source of what works and what doesn't. It is not the place to hide transitional phases. Moreover, the least possible value you could provide to users is to gratuitously[*] change the syntax and not tell anyone about it. [*] It's not like this will magically gain us MySQL or Oracle compatibility. In fact, the recent trend in the SQL commands has been to accept most options in any order, so it would only be logical to accept the LIMIT and FOR UDPATE options in any order and document that fact. There is a separate section in each reference page for information about which format is compatible with what. But please remember that our foremost goal is to be compatible, both in actuality and in mindset, with PostgreSQL, not with any other product that happened to use a slightly different syntax at their whim. Therefore I request that both forms be accepted and documented as equally valid. -- Peter Eisentraut peter_e@gmx.net