Re: pg_restore option --clean
От | Fabrice Chapuis |
---|---|
Тема | Re: pg_restore option --clean |
Дата | |
Msg-id | CAA5-nLAvRTdqdpX_M=oWUxdUDcAUKa-PrCS-pbhAeP9KJ5XmKA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_restore option --clean (M Sarwar <sarwarmd02@outlook.com>) |
Ответы |
Re: pg_restore option --clean
|
Список | pgsql-admin |
But it does not work for the structure
# CONSTRAINT test FOREIGN KEY (id_tab_key) REFERENCES tab(id) ON DELETE cascade ON UPDATE CASCADE
ERROR: cannot drop table tab because other objects depend on it
Regards,
Fabrice
On Wed, Feb 21, 2024 at 12:47 PM M Sarwar <sarwarmd02@outlook.com> wrote:
Look around forALTER TABLE TABLE-NAMEADD constraint fk-name foreign key col-name refers to tab-name ( col-name )on UPDATE cascaseon DELETE CASCADE;Good luck,SarwarFrom: Fabrice Chapuis <fabrice636861@gmail.com>
Sent: Wednesday, February 21, 2024 4:17 AM
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Fwd: pg_restore option --cleanHi,The --clean option of pg_restore allows you to replace an object before being imported. However, dependencies such as foreign keys or views prevent the deletion of the object. Is there a way to add the cascade option to force the deletion?Thanks for helpingFabrice
В списке pgsql-admin по дате отправления: