| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Thomas Poty <thomas(dot)poty(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: raising error when max length of sql object's name reached |
| Date: | 2018-03-28 17:57:15 |
| Message-ID: | CAKFQuwYNYSUYzo1pL0E4a==R-jye09Dpzo0J4Scek+8MzECF-Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Poty | 2018-03-28 18:50:58 | Re: raising error when max length of sql object's name reached |
| Previous Message | Thomas Poty | 2018-03-28 17:41:23 | raising error when max length of sql object's name reached |