Re: Implementation of LIMIT on DELETE and UPDATE statements (rel to 7.2.1)
От | Alvaro Herrera |
---|---|
Тема | Re: Implementation of LIMIT on DELETE and UPDATE statements (rel to 7.2.1) |
Дата | |
Msg-id | 20020921193503.7bf3ed2c.alvherre@atentus.com обсуждение исходный текст |
Ответ на | Re: Implementation of LIMIT on DELETE and UPDATE statements (rel to 7.2.1) (srb@cuci.nl (Stephen R. van den Berg)) |
Ответы |
Re: Implementation of LIMIT on DELETE and UPDATE statements (rel to 7.2.1)
|
Список | pgsql-patches |
En Sun, 22 Sep 2002 01:19:24 +0200 srb@cuci.nl (Stephen R. van den Berg) escribió: > Incidentally, using a SELECT without an ORDER BY but with a LIMIT is > documented to give unpredictable results, yet users are expected cope with > this fact, but are expected to have problems with a similar fact in > an UPDATE or DELETE statement? > Somehow the argumentation is not conclusive. Yes, I was thinking the same thing when I answered earlier. I am in the same position as you here (meaning someone who has contributed some patch), so my opinion doesn't have a lot of weigth; but as I already said, the feature has some value with the ORDER BY added, and the LIMIT/OFFSET thing expanded to allow expressions (this last part is in TODO). Clearly an ORDER BY clause without LIMIT doesn't make any sense; but it does with it. -- Alvaro Herrera (<alvherre[a]atentus.com>) "Para tener mas hay que desear menos"
В списке pgsql-patches по дате отправления: