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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok, thanks for information
Thomas

Le mer. 28 mars 2018 à 19:57, David G. Johnston <david.g.johnston@xxxxxxxxx> a écrit :
On Wednesday, March 28, 2018, Thomas Poty <thomas.poty@xxxxxxxxx> 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.


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux