From: | Jonathan Gardner <jgardner(at)jonathangardner(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | ALTER TABLE ... TO ... to change related names |
Date: | 2003-08-30 15:32:36 |
Message-ID: | 200308300832.43520.jgardner@jonathangardner.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've always wanted to be a PoatgreSQL hacker, and I am going to try this
change out first. Bruce said that it's kind of low on the priority list, so
hopefully I won't be holding anyone up if I take a while to get it right.
The bug is that when you craete a table with a "SERIAL" column, and/or a
"PRIMARY KEY", and then change that table's name via "ALTER TABLE", the
related sequence and primary key index do not change their names
accordingly.
I think the change is simple -- just update the names of the related
sequences and indexes when the table name changes. Of course, the entire
operation will have to be done in a transaction block.
I'm playing with the CVS version of PostgreSQL right now -- compiling it and
testing it. In the meantime, I am coming up with some unit tests to
determine whether I succeed or not.
Any comments about the project and its scope?
- --
Jonathan Gardner
jgardner(at)jonathangardner(dot)net
Live Free, Use Linux!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/UMOZWgwF3QvpWNwRAtFRAJ9imFuhSzneNCEL5PBmV2EtajCNWACgpKab
tON4nCyOKhsIujtlAFhjEDU=
=VZeU
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Matt Clark | 2003-08-30 15:36:20 | Re: Hardware recommendations to scale to silly load |
Previous Message | Andrew Dunstan | 2003-08-30 15:16:02 | Re: Linux2.6 overcommit behaviour |