Thread: raising error when max length of sql object's name reached

raising error when max length of sql object's name reached

From
Thomas Poty
Date:
Hi Community,

Currently I works with a 9.6.7 and  I wonder If PostgreSQL could raise an error instead of truncate the name of a SQL object (eg: a column name, an alias for a column in select statement , a table name, etc...)    when the length exceed 63 characters? 

Many Thanks 

Thomas 


Re: raising error when max length of sql object's name reached

From
"David G. Johnston"
Date:
On Wednesday, March 28, 2018, Thomas Poty <thomas.poty@gmail.com> wrote:
Hi Community,

Currently I works with a 9.6.7 and  I wonder If PostgreSQL could raise an error instead of truncate the name of a SQL object (eg: a column name, an alias for a column in select statement , a table name, etc...)    when the length exceed 63 characters? 

Last discussion I found was 2012.


In short, it likely will never be the new default and an option to control it is undesirable.  This would be better addressed as part of static analysis at this point.

David J.

Re: raising error when max length of sql object's name reached

From
Thomas Poty
Date:
Ok, thanks for information
Thomas

Le mer. 28 mars 2018 à 19:57, David G. Johnston <david.g.johnston@gmail.com> a écrit :
On Wednesday, March 28, 2018, Thomas Poty <thomas.poty@gmail.com> wrote:
Hi Community,

Currently I works with a 9.6.7 and  I wonder If PostgreSQL could raise an error instead of truncate the name of a SQL object (eg: a column name, an alias for a column in select statement , a table name, etc...)    when the length exceed 63 characters? 

Last discussion I found was 2012.


In short, it likely will never be the new default and an option to control it is undesirable.  This would be better addressed as part of static analysis at this point.

David J.