Jeff Synnestvedt ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
CREATE TABLE with long table name and long serial column name can cause conflicting
sequence naming
Long Description
When two tables are named with similiar names and those tables also have declarations
of a serial column with long (again similiar names) postgresql returns the error(this
is the error from my example code when run from psql):
ERROR: Relation 'tablewithreal_tableidwithre_seq' already exists
I am running version:
version
-------------------------------------------------------------
PostgreSQL 7.1.3 on i686-pc-linux-gnu, compiled by GCC 2.96
(1 row)
on distribution 7.2 of RedHat linux kernel 2.4.7-10
Sample Code
CREATE TABLE tablewithreallylongname(
tableidwithreallylongname serial NOT NULL UNIQUE PRIMARY KEY
);
CREATE TABLE tablewithreallylongname2(
tableidwithreallylongname serial NOT NULL UNIQUE PRIMARY KEY
);
No file was uploaded with this report
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
