Are the constraints deferrable?
If they are, then you can replace the data with a single transaction.
If not, then you'll have to look at disabling triggers for the update.
On Fri, 2005-05-13 at 14:55, Mark Fenbers wrote:
> True, but Counties has about 8 or 9 rules, view, or pk constraints
> attached to it. I don't want to break all these unless I knew of a
> way to save off the SQL for them beforehand so I can easily rebuild
> them...
> Mark
>
> Ing. Jhon Carrillo wrote:
> > Use Drop table YOUR_TABLE cascade
> >
> > Jhon Carrillo
> > Ingeniero en Computación
> > Caracas - Venezuela
> >
> >
> >
> > ----- Original Message -----
> > From: Mark Fenbers
> > To: pgsql-sql@postgresql.org
> > Sent: Friday, May 13, 2005 2:38 PM
> > Subject: [SQL] Replacing a table with constraints
> >
> > I have a table called Counties which partially contains a
> > lot bad data. By" bad data", I mean some records are
> > missing; some exist and shouldn't; and some records have
> > fields with erroneous information. However, the majority of
> > the data in the table is accurate. I have built/loaded a
> > new table called newCounties with the same structure as
> > Counties, but contains no bad data. My was to completely
> > replace the contents of Counties with the contents of
> > newCounties. The problem is: several other tables have
> > Foreign Key constraints placed on Counties. Therefore, Pg
> > will not let me 'DELETE FROM Counties;", nor will it let me
> > "DROP TABLE Counties;"
> >
> > I'm perplexed. Can someone suggest how I can best get data
> > from Counties to look just like newCounties?
> >
> > Mark
> >
> >
> >
> > ____________________________________________________________
> > ---------------------------(end of
> > broadcast)---------------------------
> > TIP 8: explain analyze is your friend
>
>
> ______________________________________________________________________
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
