| From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | George Essig <george(dot)essig(at)gmail(dot)com>, "pobox(at)verysmall(dot)org" <pobox(at)verysmall(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: RI_ConstraintTrigger question |
| Date: | 2005-09-27 19:34:46 |
| Message-ID: | 43399ED6.4050000@Yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/27/2005 3:27 PM, Tom Lane wrote:
> Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
>> On 9/27/2005 12:20 AM, George Essig wrote:
>>>> We have a database with about 30 tables and some RI. The RI constraints,
>>>> however, were not named upon creation of the database 2-3 years ago and
>>>> now when we get an error it contains <unnamed> for the constraint.
>
>> What you could do is to dump the database, edit the dump and restore it.
>
> Why not just drop and re-add the FK constraints?
Dropping unnamed constraints can be a bit tedious.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pobox@verysmall.org | 2005-09-28 00:20:44 | Re: RI_ConstraintTrigger question |
| Previous Message | Tom Lane | 2005-09-27 19:27:11 | Re: RI_ConstraintTrigger question |