Re: DELETE CASCADE
От | Peter Eisentraut |
---|---|
Тема | Re: DELETE CASCADE |
Дата | |
Msg-id | 1f5bcf95-d24c-b8c8-542e-47ad10ff2ddf@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: DELETE CASCADE (David Christensen <david.christensen@crunchydata.com>) |
Ответы |
Re: DELETE CASCADE
|
Список | pgsql-hackers |
On 08.06.21 21:25, David Christensen wrote: > I sense more complicated concurrency and permission issues, however. > > Assuming this happens in the same transaction, wouldn't this just work? > Or are you thinking there needs to be some sort of predicate lock to > prevent a concurrent add of the referencing record in the FK table? It might work, I'm just saying it needs to be thought about carefully. If you have functionality like, delete this if there is no matching record over there, you need to have the permission to check that and need to make sure it stays that way.
В списке pgsql-hackers по дате отправления: