MIME-Version: 1.0
In-Reply-To: <2808875.1714794677@sss.pgh.pa.us>
References: <CAEs=6DnMQCAF_c+=Vup8qnOM1OT1GfFq6nzGF2a3EhgnyrjpMg@mail.gmail.com>
 <CABUevEwkSS_FhL0Zi1_m3oU5WqELHF+qQfCLDK3e__qTsYdsYw@mail.gmail.com>
 <7c3a1c91-566a-46f7-82b5-b47eac58c500@aklaver.com> <2746167.1714770911@sss.pgh.pa.us>
 <CACJufxF=VJ=wprULGXLuAaSt5j+4w0=66HzKDQ9GEKFXMo1-bg@mail.gmail.com> <2808875.1714794677@sss.pgh.pa.us>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Fri, 3 May 2024 21:06:20 -0700
Message-ID: <CAKFQuwbLcGQHw+catBy65FyKsD6zm9z2=94RecqYSVcyBverwg@mail.gmail.com>
Subject: Re: \dt shows table but \d <table> says the table doesn't exist ?
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: jian he <jian.universality@gmail.com>, Adrian Klaver <adrian.klaver@aklaver.com>, 
	Magnus Hagander <magnus@hagander.net>, David Gauthier <dfgpostgres@gmail.com>, 
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000007296c1061798f5ae"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwbLcGQHw%2BcatBy65FyKsD6zm9z2%3D94RecqYSVcyBverwg%40mail.gmail.com>
Precedence: bulk

--0000000000007296c1061798f5ae
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Friday, May 3, 2024, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>
> By and large, I'd expect people using mixed-case table names to get
> accustomed pretty quickly to the fact that they have to double-quote
> those names in SQL.  I don't see why it's a surprise that that is also
> true in \d commands.
>
>
Every day the number of people increases who get mixed-case names in their
DB because their client language preserves case and doesn=E2=80=99t require=
 quoting.

And it isn=E2=80=99t like any sane person is using case to distinguish name=
s in
their DB and so would be at risk of seeing multiple unwanted matches for
any given pattern.

I don=E2=80=99t think name pattern matching during object lookup is a good =
tool to
wield to try and convince people that using camel case is a bad idea and
they should use snake case instead.  If they don=E2=80=99t write enough raw=
 SQL to
be annoyed by their choice more power to them, making \d more accessible
for them is a win and snake case people won=E2=80=99t notice or care.

David J.

--0000000000007296c1061798f5ae
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Friday, May 3, 2024, Tom Lane &lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">t=
gl@sss.pgh.pa.us</a>&gt; wrote:<blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
By and large, I&#39;d expect people using mixed-case table names to get<br>
accustomed pretty quickly to the fact that they have to double-quote<br>
those names in SQL.=C2=A0 I don&#39;t see why it&#39;s a surprise that that=
 is also<br>
true in \d commands.<br><br>
</blockquote><div><br></div><div>Every day the number of people increases w=
ho get mixed-case names in their DB because their client language preserves=
 case and doesn=E2=80=99t require quoting.</div><div><br></div><div>And it =
isn=E2=80=99t like any sane person is using case to distinguish names in th=
eir DB and so would be at risk of seeing multiple unwanted matches for any =
given pattern.</div><div><br></div><div>I don=E2=80=99t think name pattern =
matching during object lookup is a good tool to wield to try and convince p=
eople that using camel case is a bad idea and they should use snake case in=
stead.=C2=A0 If they don=E2=80=99t write enough raw SQL to be annoyed by th=
eir choice more power to them, making \d more accessible for them is a win =
and snake case people won=E2=80=99t notice or care.</div><div><br></div><di=
v>David J.</div>

--0000000000007296c1061798f5ae--