Re: regclass error reports improperly downcased - Mailing list pgsql-hackers

From Greg Stark
Subject Re: regclass error reports improperly downcased
Date
Msg-id CAM-w4HOQyq0Pcgb97FGw=NmDtHx2ohonLiG0Xuga5MnoHRXE+Q@mail.gmail.com
Whole thread Raw
In response to regclass error reports improperly downcased  (Jim Nasby <jnasby@enova.com>)
List pgsql-hackers
<div dir="ltr"><div class="gmail_extra"><br /><div class="gmail_quote">On Fri, Nov 8, 2013 at 12:29 AM, Jim Nasby <span
dir="ltr"><<ahref="mailto:jnasby@enova.com" target="_blank">jnasby@enova.com</a>></span> wrote:<br /><blockquote
class="gmail_quote"style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":6vq"
style="overflow:hidden">decibel@decina.cashnetusa=# SELECT 'Moo'::regclass;<br /> ERROR:  relation "moo" does not exist
atcharacter 8<br /><br /> Obviously in this example it doesn't matter, but this can definitely confuse
users.</div></blockquote></div><br/></div><div class="gmail_extra">I would actually say *not* downcasing would be more
likelyto 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
whatthey've done wrong.<br /></div><div class="gmail_extra"><br clear="all" /><br />-- <br />greg<br /></div></div> 

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: regclass error reports improperly downcased
Next
From: Tom Lane
Date:
Subject: Re: regclass error reports improperly downcased