7.3 will partially fix this issue by extending the length of the NAME
data type.
Ie. You won't hit it until you have large (32+ character) length names.
On Tue, 2002-09-03 at 16:31, [EMAIL PROTECTED] wrote:
> Søren Laursen ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> Error on create a new sequence by using the create table command.
>
> Long Description
> In postgresql 7.1 and 7.2.1:
>
> Then using a statement like:
> CREATE TABLE longtablename(
> longtablenamenr serial NOT NULL UNIQUE PRIMARY KEY,....
>
> )
>
> and later a
> CREATE TABLE longtablenamestep(
> longtablenamestepnr serial NOT NULL UNIQUE PRIMARY KEY,....
>
> )
>
> I get an error on creating the last table. This is because the new sequence is named
>with the same name as the one used by the first table. The create statement is then
>terminated and no table is created. I would have to create the sequence my self and
>then create the table using statements like:
> not null default nextval('"longtablename_longtablename_sq1"'::text).
>
> Regards,
>
> Soeren Laursen
>
>
> Sample Code
>
>
> No file was uploaded with this report
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
