| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: temporarily disabling foreign keys |
| Date: | 2011-05-10 18:34:37 |
| Message-ID: | 4DC9853D.90607@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 05/10/11 11:12 AM, Seb wrote:
> Hi,
>
> I'm not sure how best to handle this situation. The tables in a
> database need to be completely cleared and copy'ed into about every few
> months, as they are updated with new records and corrections from a
> provider. Because the tables have foreign key constraints with 'ON
> UPDATE CASCADE ON DELETE RESTRICT', it's not possible to DELETE them
> without violating these constraints. I've been dropping the constraints
> while doing these transactions and then recreating them once everything
> is done, but this has gotten tedious. Is there some way to "disable"
> the foreign keys and enabling them after the transactions? Thanks.
might be faster to just drop the tables and recreate them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2011-05-10 18:39:08 | Re: temporarily disabling foreign keys |
| Previous Message | Vick Khera | 2011-05-10 18:29:48 | Re: temporarily disabling foreign keys |