From: | Tim Wilson <wilson(at)visi(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: remnants of deleted table causing problems |
Date: | 2002-05-28 19:13:16 |
Message-ID: | 20020528191316.GB28402@isis.visi.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Tue, May 28, 2002 at 03:03:37PM -0400, Tom Lane wrote:
> Tim Wilson <wilson(at)visi(dot)com> writes:
> > I used 'new_event' as the name of the newly created 'event' table. I
> > subsequently renamed it back to 'event'. I've looked all through the
> > database looking for rogue references to 'new_event', but I can't find
> > any.
>
> I'd bet on a referential integrity trigger causing the problem. Up till
> very recently, RENAME TABLE wasn't smart enough to adjust RI trigger
> parameters. (Don't recall if the fix is in 7.2 or not; it may only be
> in development sources.)
So I should drop the 'location_exists' constraint in the 'event' table
and recreate it?
-Tim
--
Tim Wilson | Visit Sibley online: | Check out:
Henry Sibley HS | http://www.isd197.org | http://www.zope.com
W. St. Paul, MN | | http://slashdot.org
wilson(at)visi(dot)com | <dtml-var pithy_quote> | http://linux.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-05-28 19:22:51 | Re: remnants of deleted table causing problems |
Previous Message | Tom Lane | 2002-05-28 19:03:37 | Re: remnants of deleted table causing problems |