Re: [SQL] LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [SQL] LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?
Date
Msg-id 200208290114.g7T1EGO29372@candle.pha.pa.us
Whole thread Raw
In response to Re: [SQL] LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [SQL] LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?
Re: [SQL] LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?
List pgsql-hackers
Tom Lane wrote:
> >> If you would like a vote, we can do that, but as I remember we had the
> >> same issue with COPY and we got most votes to just show the best syntax.
> 
> Perhaps we could compromise on showing only the new syntax in the <synopsis>
> part of the man page, and then mentioning somewhere in the body of the
> page that the other order is deprecated but accepted for backwards
> compatibility.  This same approach would work well for documenting
> COPY's old syntax.

Yes, I thought about that.  People want to show both SELECT syntaxes,
but how would you do that --- show the SELECT syntax twice with just
those last two clauses reversed --- yuck.

We could easily mention that we allow both clause orderings in the text
somewhere.

For COPY, we could just put the old syntax at the bottom of the manual
page and mention it is depricated.

--  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,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: VIRUS IN YOUR MAIL (W32/Klez.h@MM)
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] fix for palloc() of user-supplied length