Re: DELETE CASCADE

Поиск
Список
Период
Сортировка
От David Christensen
Тема Re: DELETE CASCADE
Дата
Msg-id 2493162B-45AE-4810-97A0-0A65F49FD41C@crunchydata.com
обсуждение исходный текст
Ответ на Re: DELETE CASCADE  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Ответы Re: DELETE CASCADE  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Список pgsql-hackers
> On Jun 5, 2021, at 2:29 AM, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
>
> On 04.06.21 22:24, David Christensen wrote:
>> So what are the necessary and sufficient conditions to check at this point?  The constraint already exists, so what
permissionswould we need to check against which table(s) in order to grant this action? 
>
> I think you would need DELETE privilege on all affected tables.

So basically where we are dispatching to the CASCADE guts, first check session user’s DELETE permission and throw the
normalpermissions error if they can’t delete? 



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

Предыдущее
От: Isaac Morland
Дата:
Сообщение: Re: DELETE CASCADE
Следующее
От: vignesh C
Дата:
Сообщение: Re: Added schema level support for publication.