| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, jian he <jian(dot)universality(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, David Gauthier <dfgpostgres(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: \dt shows table but \d <table> says the table doesn't exist ? |
| Date: | 2024-05-04 04:47:23 |
| Message-ID: | CAKFQuwaL-vb93NB7cFRcLNE_uoUcYAW++r9VGbhnzqWDh4S9FQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday, May 3, 2024, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
> Have you met people?
>
I really don’t care enough to try and actually make converts here. It
would have been a perfectly justifiable design choice to make our “pattern”
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’s a find
feature and search benefits from case-insensitivity. There isn’t anything
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’d welcome
a modifier like “*” (like the ~* operator) to enable case-insensitive
matching.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-05-04 04:57:55 | Re: \dt shows table but \d <table> says the table doesn't exist ? |
| Previous Message | Adrian Klaver | 2024-05-04 04:22:55 | Re: \dt shows table but \d <table> says the table doesn't exist ? |