-----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
[EMAIL PROTECTED]
Live Free, Use Linux!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/UMOZWgwF3QvpWNwRAtFRAJ9imFuhSzneNCEL5PBmV2EtajCNWACgpKab
tON4nCyOKhsIujtlAFhjEDU=
=VZeU
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
