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

Ok, thanks for information
Thomas

Le mer. 28 mars 2018 à 19:57, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
a écrit :

> On Wednesday, March 28, 2018, Thomas Poty <thomas(dot)poty(at)gmail(dot)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.
>
>
> http://www.postgresql-archive.org/Prepared-Statement-Name-Truncation-td5732574.html
>
> 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.
>
>