Re: LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?

From: Magnus Enbom <dot(at)rockstorm(dot)se>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?
Date: 2002-08-26 19:50:27
Message-ID: 20020826215027.A15218@ford.rockstorm.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

On Mon, Aug 26, 2002 at 02:42:26PM -0400, Jan Wieck wrote:
> Bruce Momjian wrote:
> >
> > I found this email from April. It properly points out that our
> > LIMIT/FOR UPDATE ordering doesn't match MySQL's, and MySQL's looks more
> > correct, specifically that the FOR UPDATE is after the LIMIT. Our
> > grammar is:
>
> How do you define "correct" for "non-standard" features? And why don't
> you ask Monty first to change to our "de-facto-standard"? ;-)

Already done that. ;-)
He said he would look into it(having MySQL accept both behaviors), but if
it would require a big change of their grammar(for a value of big), he'd rather
not. He also pointed out(as Bruce and Tom have done) that our(PG) way is
kind of backwards.
If you look at Oracle, you can see that they also have it last:

select :== subquery -> for_update_clause ;

OTOH, Oracle doesn't have LIMIT, but that's another story...

-- Magnus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2002-08-26 19:52:13 Re: anonymous composite types - how to pass tupdesc to
Previous Message Tom Lane 2002-08-26 19:11:04 Re: anonymous composite types - how to pass tupdesc to the function

Browse pgsql-sql by date

  From Date Subject
Next Message Bruce Momjian 2002-08-26 19:54:48 Re: LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?
Previous Message Tom Lane 2002-08-26 19:01:37 Re: LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?