Re: PL/PgSQL STRICT

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: PL/PgSQL STRICT
Дата
Msg-id CAFj8pRDJEE0P9Wz0BUcvt8OrLYJpyuZ+4GtB0z5eBGLeaAA3Fw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: PL/PgSQL STRICT  (Marko Tiikkaja <pgmail@joh.to>)
Список pgsql-hackers
2012/12/21 Marko Tiikkaja <pgmail@joh.to>:
> On 12/21/12 4:49 PM, I wrote:
>>
>> On 12/21/12 4:39 PM, Tom Lane wrote:
>>>
>>> What is the use-case for this?
>>
>>
>> Currently, the way to do this would be something like:
>
>
> I realize I didn't really answer the question.
>
> The use case is when you're UPDATEing or DELETEing a row and you want to
> quickly assert that there should be exactly one row.  For example, if you've
> previously locked a row with SELECT .. FOR UPDATE, and now you want to
> UPDATE or DELETE it, it better be there (or you have a bug somewhere).
>

yes, it has sense

probably only after keyword it should be simple implementable

Regards

Pavel

>
>
> Regards,
> Marko Tiikkaja
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers



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

Предыдущее
От: Marko Tiikkaja
Дата:
Сообщение: Re: PL/PgSQL STRICT
Следующее
От: Marko Kreen
Дата:
Сообщение: pgcrypto seeding problem when ssl=on