Re: PL/PgSQL STRICT
| От | Marko Tiikkaja |
|---|---|
| Тема | Re: PL/PgSQL STRICT |
| Дата | |
| Msg-id | 50D485D0.5050201@joh.to обсуждение исходный текст |
| Ответ на | Re: PL/PgSQL STRICT (Marko Tiikkaja <pgmail@joh.to>) |
| Ответы |
Re: PL/PgSQL STRICT
Re: PL/PgSQL STRICT |
| Список | pgsql-hackers |
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). Regards, Marko Tiikkaja
В списке pgsql-hackers по дате отправления: