From: | erobles <erobles(at)sensacd(dot)com(dot)mx> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: NOTICE: ignoring incomplete trigger group for constraint |
Date: | 2010-05-22 16:03:33 |
Message-ID: | 4BF80055.7010409@sensacd.com.mx |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/21/2010 11:18 AM, Tom Lane wrote:
>
> Yeah, this is known to happen in some cases where there was a broken
> (incompletely enforced) foreign key constraint in your old database.
> The odds are good that what you should do is nothing at all, because
> you probably didn't even realize you still had the FK constraint in the
> old database: the most common error cases weren't enforced. It's likely
> that if you try to add the FK constraint now, you'll find it fails
> because the data doesn't even satisfy the constraint. So you could
> just leave things alone and the new database will behave approximately
> like the old one did. But if you really want to add the FK constraint
> back in, ALTER TABLE ADD FOREIGN KEY is the way.
>
>
hi, i made the alter table to add the foreign key, but in some
constraints i have the follow error:
ERROR: there is no unique constraint matching given keys for referenced
table "table_name'"
there is a way to solve this?? what can i do ??
regards, erobles
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2010-05-22 16:17:39 | Re: NOTICE: ignoring incomplete trigger group for constraint |
Previous Message | Merlin Moncure | 2010-05-22 15:25:29 | Re: Select max(primary_key) taking a long time |