Re: SELECT FOR UPDATE and LIMIT 1 behave oddly

Поиск
Список
Период
Сортировка
От Josh Berkus
Тема Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Дата
Msg-id 200411110955.35094.josh@agliodbs.com
обсуждение исходный текст
Ответ на SELECT FOR UPDATE and LIMIT 1 behave oddly  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: SELECT FOR UPDATE and LIMIT 1 behave oddly  (andrea suisani <suisani@demetra.com>)
Список pgsql-bugs
Bruce,

Ah, yes, which reminds me I need to generate that doc patch.

> I am wondering if a documentation warning about the use of FOR UPDATE
> and LIMIT is a good idea.  If we can't be sure the LIMIT will return a
> guaranteed number of rows, should we just disallow that combination?  I
> realize such a case is rare.  Should we emit a warning when it happens?

Well, limit+for update can be useful under some circumstances, as long as you
understand its limitations.    We found a workaround.  So I'd oppose
disallowing it.

--
Josh Berkus
Aglio Database Solutions
San Francisco

В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Magnus Hagander"
Дата:
Сообщение: Re: BUG #1312: the ordinal 2821 could not be located
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: SELECT FOR UPDATE and LIMIT 1 behave oddly