Feedback-ID: i76984098:Fastmail
Message-ID: <8a888f00-3752-463e-87c6-bb3979c7a4b8@aklaver.com>
Date: Fri, 3 May 2024 21:22:55 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: \dt shows table but \d <table> says the table doesn't exist ?
To: "David G. Johnston" <david.g.johnston@gmail.com>,
 Tom Lane <tgl@sss.pgh.pa.us>
Cc: jian he <jian.universality@gmail.com>,
 Magnus Hagander <magnus@hagander.net>, David Gauthier
 <dfgpostgres@gmail.com>,
 "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
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>
 <CAKFQuwbLcGQHw+catBy65FyKsD6zm9z2=94RecqYSVcyBverwg@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAKFQuwbLcGQHw+catBy65FyKsD6zm9z2=94RecqYSVcyBverwg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/8a888f00-3752-463e-87c6-bb3979c7a4b8%40aklaver.com>
Precedence: bulk

On 5/3/24 21:06, David G. Johnston wrote:
> On Friday, May 3, 2024, Tom Lane <tgl@sss.pgh.pa.us 
> <mailto: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’t 
> require quoting.

In a sense they do by making quoting the default, which people find out 
when they stray from the language/ORM/framework and get pointed at:

https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS

> 
> And it isn’t like any sane person is using case to distinguish names in 
> their DB and so would be at risk of seeing multiple unwanted matches for 
> any given pattern.

Have you met people?

> 
> I don’t 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’t 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’t notice or care.
> 
> David J.

-- 
Adrian Klaver
adrian.klaver@aklaver.com