Postgres Pro
Downloads
Home   >   mailing lists

Re: raising error when max length of sql object's name reached - Mailing list pgsql-admin

From David G. Johnston
Subject Re: raising error when max length of sql object's name reached
Date
Msg-id CAKFQuwYNYSUYzo1pL0E4a==R-jye09Dpzo0J4Scek+8MzECF-Q@mail.gmail.com
Whole thread Raw
In response to raising error when max length of sql object's name reached  (Thomas Poty <thomas.poty@gmail.com>)
Responses Re: raising error when max length of sql object's name reached  (Thomas Poty <thomas.poty@gmail.com>)
List pgsql-admin
Tree view
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.

pgsql-admin by date:

Previous
From: Thomas Poty
Date:
Subject: raising error when max length of sql object's name reached
Next
From: Thomas Poty
Date:
Subject: Re: raising error when max length of sql object's name reached