PostgreSQL appears to truncate column alias names after 31 characters.
| От | Manish Singh |
|---|---|
| Тема | PostgreSQL appears to truncate column alias names after 31 characters. |
| Дата | |
| Msg-id | 1158363234.5085080.1727766363469.JavaMail.zimbra@india.corelynx.com обсуждение исходный текст |
| Ответы |
Re: PostgreSQL appears to truncate column alias names after 31 characters.
|
| Список | pgsql-bugs |
Hello,
I am using pgsql with laravel.I have noticed that PostgreSQL appears to truncate column alias names
after 31 characters.
after 31 characters.
For example (this is from the psql command-line tool):
SELECT rss_headline_id as abcdefghijklmno pqrstuvwxyz1234 56, title, url
FROM news_rss_headli nes headlines WHERE rss_headline_id = 22833;
NOTICE: identifier "abcdefghijklmn opqrstuvwxyz123 456" will be
truncated to "abcdefghijklmn opqrstuvwxyz123 45"
Granted, having alias names this long may seem a little goofy, but I
am working on an object Persistence Layer that has the capability of
sometimes generating long aliases behind the scenes.
Does anyone know if this is a known limitation to PostgreSQL ? (I
couldn't find any documentation which specifically addresses this
issue) Is there a way to make PostreSQL support longer alias names?
Are there any plans to address this in future version of PostgreSQL?
Or... should I just "suck it up" and fix my code? ;-).
SELECT rss_headline_id as abcdefghijklmno pqrstuvwxyz1234 56, title, url
FROM news_rss_headli nes headlines WHERE rss_headline_id = 22833;
NOTICE: identifier "abcdefghijklmn opqrstuvwxyz123 456" will be
truncated to "abcdefghijklmn opqrstuvwxyz123 45"
Granted, having alias names this long may seem a little goofy, but I
am working on an object Persistence Layer that has the capability of
sometimes generating long aliases behind the scenes.
Does anyone know if this is a known limitation to PostgreSQL ? (I
couldn't find any documentation which specifically addresses this
issue) Is there a way to make PostreSQL support longer alias names?
Are there any plans to address this in future version of PostgreSQL?
Or... should I just "suck it up" and fix my code? ;-).
Please suggest me how can i solve this problem.I can not switch my RDBMS from PGSQL to others
Any insights or comments would be appreciated.
Thanks,
Any insights or comments would be appreciated.
Thanks,
Manish Kumar Singh
В списке pgsql-bugs по дате отправления: