From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: question on renaming a foreign key |
Date: | 2006-10-12 00:04:34 |
Message-ID: | 452D8692.5070400@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/11/06 18:53, Richard Broersma Jr wrote:
>>>> can anyone suggest a non-nightmarish way for me to do this
>>>> ?
>>> If your tables are setup to "ON UPDATE CASCASE" then you are
>>> fine. Just updated the main table and PostgreSQL will take
>>> care of the rest.
>
>> I doesn't appear that ALTER TABLE can change constraint
>> characteristics. You'd have to drop/recreate, no?
>
> Now that you mention it, I've never tried it or seen it done.
> Here I what I came up with:
>
[snip]
>
>
> It is nice to see things work so well. :-)
It would be interesting to see how well it works on a 50M row table.
- --
Ron Johnson, Jr.
Jefferson LA USA
Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFLYaSS9HxQb37XmcRAmO+AKDH1ILeOKJEYitfY6LUTrRZKjk33wCdGIZW
ZN0L1iAJphWTNGlAoz63E3E=
=3zQr
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Geoffrey | 2006-10-12 00:10:22 | Re: more anti-postgresql FUD |
Previous Message | Tom Lane | 2006-10-11 23:58:53 | Re: database corruption question |