Hi. Thanks for responding.
I don't *think* there are circular references, but the nature of the
problem is that the code doesn't know anything about the semantics of
the schema - it just gets the list of tables, and there are multiple
schemas it needs to handle, all of which may change over time. That's
why I was hoping for some kind of global "disable constraints" command.
I guess it should be possible to generate the proper table order based
on loading up all of the constraints from the catalog. It seems like
more trouble than I want to go to for this problem, but maybe it
wouldn't be too difficult...
- DAP
>-----Original Message-----
>From: pgsql-general-owner@postgresql.org
>[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Vivek Khera
>Sent: Thursday, November 04, 2004 3:05 PM
>To: pgsql-general@postgresql.org
>Subject: Re: [GENERAL] disabling constraints
>
>>>>>> "DP" == David Parker <dparker@tazznetworks.com> writes:
>
>DP> I would like to be able to truncate all of the tables in a schema
>DP> without worrying about FK constraints. I tried issuing a "SET
>DP> CONSTRAINTS ALL DEFERRED" before truncating, but I still get
>DP> constraint errors. Is there a way to do something like:
>
>Why don't you truncate your tables in an order that won't
>violate FK's? Or do you have circular references?
>
>--
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>Vivek Khera, Ph.D. Khera Communications, Inc.
>Internet: khera@kciLink.com Rockville, MD +1-301-869-4449 x806
>AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
>
>---------------------------(end of
>broadcast)---------------------------
>TIP 8: explain analyze is your friend
>
