Re: LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1?
От | Vivek Khera |
---|---|
Тема | Re: LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1? |
Дата | |
Msg-id | x7n0r7huju.fsf@onceler.kciLink.com обсуждение исходный текст |
Ответ на | Re: LIMIT 1 FOR UPDATE or FOR UPDATE LIMIT 1? (Bruce Momjian <pgman@candle.pha.pa.us>) |
Список | pgsql-sql |
>>>>> "BM" == Bruce Momjian <pgman@candle.pha.pa.us> writes: BM> OK, no one has commented on this, so I guess I am going to have to guess BM> the group's preference. BM> My guess, seeing as very few probably use LIMIT and FOR UPDATE together, BM> is to swap them and document it in the release notes. Was I correct in BM> my guess? My preference is to allow both orders for one release, then only allow the "correct" order in the next. be sure to absolutely make this a big red notice in the changelog. I just scanned my main app and found two instances where I use FOR UPDATE LIMIT 1. These are trivial to change, but difficult to do at the same moment I update the db server. One of these I probably don't even need the LIMIT... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
В списке pgsql-sql по дате отправления: