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"? ;-)
Well, MySQL created LIMIT, so they have the right to define the standard. I think FOR UPDATE looks more correct at the end because it controls the visibility of the returned result, while LIMIT and the other previous clauses control the result. FOR UPDATE clearly has a different effect than LIMIT, GROUP BY, WHERE, and the other previous clauses, so it makes more sense to me to have it at the end. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
