| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Jim Nasby <jnasby(at)enova(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Michael Elterman <melterman(at)enova(dot)com> |
| Subject: | Re: regclass error reports improperly downcased |
| Date: | 2013-11-08 00:38:17 |
| Message-ID: | CAM-w4HOQyq0Pcgb97FGw=NmDtHx2ohonLiG0Xuga5MnoHRXE+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 8, 2013 at 12:29 AM, Jim Nasby <jnasby(at)enova(dot)com> wrote:
> decibel(at)decina(dot)cashnetusa=# SELECT 'Moo'::regclass;
> ERROR: relation "moo" does not exist at character 8
>
> Obviously in this example it doesn't matter, but this can definitely
> confuse users.
>
I would actually say *not* downcasing would be more likely to confuse
users. It's actually looking for a relation named "moo". If they actually
had one named "Moo" and it said "relation "Moo" does not exist" that would
be even more confusing and less likely to result in them figuring out what
they've done wrong.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-11-08 00:41:44 | Re: regclass error reports improperly downcased |
| Previous Message | Jim Nasby | 2013-11-08 00:29:02 | regclass error reports improperly downcased |