Re: Implementation of LIMIT on DELETE and UPDATE statements
От | Jan Wieck |
---|---|
Тема | Re: Implementation of LIMIT on DELETE and UPDATE statements |
Дата | |
Msg-id | 3D90AEEF.D791F89A@Yahoo.com обсуждение исходный текст |
Ответ на | Implementation of LIMIT on DELETE and UPDATE statements (rel to 7.2.1) (srb@cuci.nl (Stephen R. van den Berg)) |
Список | pgsql-patches |
Tom Lane wrote: > > > 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? > > Well, IMHO there's a big difference in documented unpredictable output > from a documented-unpredictable query, as opposed to > documented-unpredictable changes in the database state. There is not > a lot of use for the latter AFAICS. The next thing we could implement is DELETE SOMETHING FROM SOME TABLE [OR NOT]; Very usefull for the type of programmer that needs the proposed LIMIT patch. It's the only way, those pelletheads can for sure blame the error on PostgreSQL. Sarcasm aside, folks, I am 100% with Tom here. No LIMIT on UPDATE or DELETE. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #
В списке pgsql-patches по дате отправления: