MIME-Version: 1.0
In-Reply-To: <8a888f00-3752-463e-87c6-bb3979c7a4b8@aklaver.com>
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>
 <8a888f00-3752-463e-87c6-bb3979c7a4b8@aklaver.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Fri, 3 May 2024 21:47:23 -0700
Message-ID: <CAKFQuwaL-vb93NB7cFRcLNE_uoUcYAW++r9VGbhnzqWDh4S9FQ@mail.gmail.com>
Subject: Re: \dt shows table but \d <table> says the table doesn't exist ?
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, 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>
Content-Type: multipart/alternative; boundary="00000000000042b0740617998808"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwaL-vb93NB7cFRcLNE_uoUcYAW%2B%2Br9VGbhnzqWDh4S9FQ%40mail.gmail.com>
Precedence: bulk

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

On Friday, May 3, 2024, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

>
> Have you met people?
>

I really don=E2=80=99t care enough to try and actually make converts here. =
 It
would have been a perfectly justifiable design choice to make our =E2=80=9C=
pattern=E2=80=9D
matching case-insensitive by default, probably with a case-sensitive mode
and no need to hack up quoting rules that are unique to it.  It=E2=80=99s a=
 find
feature and search benefits from case-insensitivity.  There isn=E2=80=99t a=
nything
so compelling about the current behavior that it seems like the superior
choice.  But maybe you are right and I just lack sufficient real-world
experience to see things differently.

I also get not wanting to change behavior at this point though I=E2=80=99d =
welcome
a modifier like =E2=80=9C*=E2=80=9D (like the ~* operator) to enable case-i=
nsensitive
matching.

David J.

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

On Friday, May 3, 2024, Adrian Klaver &lt;<a href=3D"mailto:adrian.klaver@a=
klaver.com">adrian.klaver@aklaver.com</a>&gt; wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><br>
Have you met people?<br>
</blockquote><div><br></div><div>I really don=E2=80=99t care enough to try =
and actually make converts here.=C2=A0 It would have been a perfectly justi=
fiable design choice to make our =E2=80=9Cpattern=E2=80=9D matching case-in=
sensitive by default, probably with a case-sensitive mode and no need to ha=
ck up quoting rules that are unique to it.=C2=A0 It=E2=80=99s a find featur=
e and search benefits from case-insensitivity.=C2=A0 There isn=E2=80=99t an=
ything so compelling about the current behavior that it seems like the supe=
rior choice.=C2=A0 But maybe you are right and I just lack sufficient real-=
world experience to see things differently.</div><div><br></div><div>I also=
 get not wanting to change behavior at this point though I=E2=80=99d welcom=
e a modifier like =E2=80=9C*=E2=80=9D (like the ~* operator) to enable case=
-insensitive matching.</div><div><br></div><div>David J.</div><div><br></di=
v>

--00000000000042b0740617998808--