Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1svXqP-00FqYs-5q for pgsql-bugs@arkaria.postgresql.org; Tue, 01 Oct 2024 08:02:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1svXqO-00Cjzp-Bi for pgsql-bugs@arkaria.postgresql.org; Tue, 01 Oct 2024 08:02:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1svWxX-00ByVG-1c for pgsql-bugs@lists.postgresql.org; Tue, 01 Oct 2024 07:06:11 +0000 Received: from ec2-50-19-124-189.compute-1.amazonaws.com ([50.19.124.189] helo=newzimbra.corelynx.com) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1svWxR-001v2N-Gq for pgsql-bugs@lists.postgresql.org; Tue, 01 Oct 2024 07:06:09 +0000 Received: from localhost (localhost [127.0.0.1]) by newzimbra.corelynx.com (Postfix) with ESMTP id 103C69891C3 for ; Tue, 1 Oct 2024 07:06:04 +0000 (UTC) Received: from newzimbra.corelynx.com ([127.0.0.1]) by localhost (newzimbra.corelynx.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id yvnOYzhSao0B for ; Tue, 1 Oct 2024 07:06:03 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by newzimbra.corelynx.com (Postfix) with ESMTP id C6DB69891C2 for ; Tue, 1 Oct 2024 07:06:03 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 newzimbra.corelynx.com C6DB69891C2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=india.corelynx.com; s=6BD109FE-8C64-11EB-BD18-1999FFC4C31E; t=1727766363; bh=tUqDdSeswyQxsoH1GgE4J7aEYZq2Lmii45avqs9st1w=; h=Date:From:To:Message-ID:MIME-Version; b=P9eWZfiProOzGwA22F8G12DWHqn3bgMtJAXmXIIAtjEOIUlg+CXB6MaFMhOai3SSM nF8FyWmGG7UgWbcqBjsxwLqusJdqJj4i8tMOHu8GsT4dsEaBIgfr5pWXes0QzjAs6x FP1HZLqUHrXMdXrXdV5HDWCaOQDExD04OP4ptCs0RF0fOQZ1XJ0/NxeG9OOtoCPbDg n169EMBJ2sHHihpGwz0zZLvTN4XrKndzBw8HLrfW4nsxjqsU9ETsbMZbpU372oa4QR g+2mc8fuPHVv8llV0E5Cl8QiuAS6qnhWnUKNJNnO5i3OEwkRP3UHfXERXXZOAg+HIz ItJkeFabaGXYQ== X-Virus-Scanned: amavisd-new at newzimbra.corelynx.com Received: from newzimbra.corelynx.com ([127.0.0.1]) by localhost (newzimbra.corelynx.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id PFYRy6HOL54o for ; Tue, 1 Oct 2024 07:06:03 +0000 (UTC) Received: from newzimbra.corelynx.com (localhost [127.0.0.1]) by newzimbra.corelynx.com (Postfix) with ESMTP id 996A49891C3 for ; Tue, 1 Oct 2024 07:06:03 +0000 (UTC) Date: Tue, 1 Oct 2024 07:06:03 +0000 (UTC) From: Manish Singh To: pgsql-bugs@lists.postgresql.org Message-ID: <1158363234.5085080.1727766363469.JavaMail.zimbra@india.corelynx.com> Subject: PostgreSQL appears to truncate column alias names after 31 characters. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_5ae7a751-6fa0-46bc-b615-b3bb81fb6e2c" X-Originating-IP: [125.20.129.34] X-Mailer: Zimbra 8.8.15_GA_4266 (ZimbraWebClient - GC121 (Linux)/8.8.15_GA_4257) Thread-Index: 4LNeX4ExyBM0XSlBUJedzE8kCC+Kgw== Thread-Topic: PostgreSQL appears to truncate column alias names after 31 characters. List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=_5ae7a751-6fa0-46bc-b615-b3bb81fb6e2c Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hello, I am using pgsql with laravel. I have noticed that PostgreSQL appears to truncate column alias names 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? ;-). 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, Manish Kumar Singh --=_5ae7a751-6fa0-46bc-b615-b3bb81fb6e2c Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hello,
I am usin= g pgsql with laravel.I have noticed that PostgreSQL appears to truncate column alia= s names
after 31 characters.

For example (this is from the psql comma= nd-line tool):
SELECT rss_headline_= id as abcdefghijklmno pqrstuvwxyz1234 56, title, url
FROM news_rss_headli nes headlines WHERE= rss_headline_id =3D 22833;
NOTICE: identifier "abcdefghijklmn opqrstuvwxyz123 456" will betruncated to "abcde= fghijklmn opqrstuvwxyz123 45"

Grant= ed, having alias names this long may seem a little goofy, but I
am working on an object Pers= istence Layer that has the capability of
sometimes generating long aliases behind the scenes.=

Does anyone know if this is a know= n limitation to PostgreSQL ? (I
couldn't find any documentation which specifically addresses = this
issue) Is the= re 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? ;-).<= /span>

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 appreci= ated.

Thanks,
Manish Kumar Sing= h
--=_5ae7a751-6fa0-46bc-b615-b3bb81fb6e2c--