From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Rod Taylor <rbt@zort.ca>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Larry Rosenman <ler@lerctr.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [SQL] LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?
Date: Wed, 28 Aug 2002 10:38:58 -0400 (EDT)
Message-ID: <200208281438.g7SEcw515550@candle.pha.pa.us> (raw)
In-Reply-To: <1030544932.83275.58.camel@jester>
Rod Taylor wrote:
> > Doesn't the need for a note explaining that we're supporting the old
> > syntax say to you that the documentation also needs to say we support
> > the old syntax? I can see the bug reports now saying "this is clearly
> > not what it says in the docs"...
>
>
> Yes, both should be documented. But mark the non-preferred version as
> depreciated and disappearing soon (whether it does or not is another
> story) but discourage people from using it.
That SELECT syntax is already too confusing. I don't want to add an
additional documentation specification that provides no value to users.
One of the PostgreSQL goals is to not throw every single option at users
but to make logical decisions on tuning values and features to limit the
complexity shown to the user.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: pgman@candle.pha.pa.us, rbt@zort.ca, xzilla@users.sourceforge.net, tgl@sss.pgh.pa.us, ler@lerctr.org, pgsql-hackers@postgresql.org
Subject: Re: [SQL] LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?
In-Reply-To: <200208281438.g7SEcw515550@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox