Re: [BUGS] BUG #8260: problem with sequence and tablename

2013-06-28 Thread Daniel Degasperi 

Am 27.06.2013 19:10, schrieb Tom Lane:

daniel.degasp...@r3-gis.com writes:

CREATE TABLE t23456789012345678901234567890123456789012345678901
(
   t1234_id serial,
   PRIMARY KEY (t1234_id)
)
WITH (
   OIDS=FALSE
);
This generated the sequence:
CREATE SEQUENCE
t2345678901234567890123456789012345678901234567890_t1234_id_seq

That's operating as designed.


The table-part in the sequence name was truncated.

Would you rather it failed entirely?  You're up against the limit on
name length (63 bytes in a standard Postgres build).
I don't know if a fail is the best solution, maybe a NOTICE, that the 
sequence name is not constructed as might be naively expected, would be 
appropriate.


thanks and regards,
Daniel



regards, tom lane



--
*Daniel Degasperi*
Project manager

*R3 GIS* Srl - GmbH

I-39012 Merano/Meran (BZ) - Via Johann Kravogl-Str. 2
I-20133 Milano (MI) - Via Vallisneri 2
web: www.r3-gis.com http://www.r3-gis.com/
Email: daniel.degasp...@r3-gis.com mailto:daniel.degasp...@r3-gis.com
Tel. : +39 0473 494949
Fax : +39 0473 069902

*ATTENZIONE!* Le informazioni contenute nella presente e-mail e nei 
documenti eventualmente allegati sono confidenziali. La loro diffusione, 
distribuzione e/o riproduzione da parte di terzi, senza autorizzazione 
del mittente è vietata e può violare il D. Lgs. 196/2003. In caso di 
ricezione per errore, Vogliate immediatamente informare il mittente del 
messaggio e distruggere la e-mail.


*ACHTUNG!* Die in dieser Nachricht oder in den beigelegten Dokumenten 
beinhalteten Informationen sind streng vertraulich. Ihre Verbreitung 
und/oder ihre Wiedergabe durch Dritte ist ohne Erlaubnis des Absenders 
verboten und verstößt gegen das Legislativdekret 196/2003. Sollten Sie 
diese Mitteilung irrtümlicherweise erhalten haben, bitten wir Sie uns 
umgehend zu informieren und anschließend die Mitteilung zu vernichten.


*WARNING!* This e-mail may contain confidential and/or privileged 
information. If you are not the intended recipient (or have received 
this e-mail in error) please notify the sender immediately and destroy 
this e-mail. Any unauthorised copying, disclousure or distribution of 
the material in this e-mail is strictly forbidden and could be against 
the law (D. Lgs. 196/2003)

[BUGS] BUG #8260: problem with sequence and tablename

2013-06-27 Thread daniel . degasperi 
The following bug has been logged on the website:

Bug reference:  8260
Logged by:  Daniel Degasperi
Email address:  daniel.degasp...@r3-gis.com
PostgreSQL version: 9.1.7
Operating system:   Centos 6.4
Description:

I've created a table:


CREATE TABLE t23456789012345678901234567890123456789012345678901
(
  t1234_id serial,
  PRIMARY KEY (t1234_id)
)
WITH (
  OIDS=FALSE
);


This generated the sequence:


CREATE SEQUENCE
t2345678901234567890123456789012345678901234567890_t1234_id_seq
  INCREMENT 1
  MINVALUE 1
  MAXVALUE 9223372036854775807
  START 1
  CACHE 1;


The table-part in the sequence name was truncated.


Best regards,
Daniel



-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #8260: problem with sequence and tablename

2013-06-27 Thread Christopher Browne 
Object names are limited to a length of NAMEDATALEN-1, which defaults to
63, and are documented to be truncated.

http://www.postgresql.org/docs/9.2/static/sql-syntax-lexical.html

The behaviour you are observing appears to conform to the documentation,
and seems reasonable, so I wouldn't think this was a bug.

Re: [BUGS] BUG #8260: problem with sequence and tablename

2013-06-27 Thread Tom Lane 
daniel.degasp...@r3-gis.com writes:
 CREATE TABLE t23456789012345678901234567890123456789012345678901
 (
   t1234_id serial,
   PRIMARY KEY (t1234_id)
 )
 WITH (
   OIDS=FALSE
 );

 This generated the sequence:

 CREATE SEQUENCE
 t2345678901234567890123456789012345678901234567890_t1234_id_seq

That's operating as designed.

 The table-part in the sequence name was truncated.

Would you rather it failed entirely?  You're up against the limit on
name length (63 bytes in a standard Postgres build).

regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs