Re: Column mis-spelling hints vs case folding - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Column mis-spelling hints vs case folding
Date
Msg-id CAM-w4HPCC5LOi2JkRTMf1=n6=xmhmr82fCB78cL10ozQjmU3Fg@mail.gmail.com
Whole thread Raw
In response to Re: Column mis-spelling hints vs case folding  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
<p dir="ltr"><br /> On 7 Apr 2015 09:37, "Robert Haas" <<a
href="mailto:robertmhaas@gmail.com">robertmhaas@gmail.com</a>>wrote:<br /> ><br /> > On Sun, Apr 5, 2015 at
12:16PM, Tom Lane <<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>> wrote:<br /> > > A newbie
errorthat we see *constantly* is misunderstanding identifier<br /> > > case-folding rules. <br /><p
dir="ltr">>> I think this hint might be a lot more useful if its comparison mechanism<br /> > > were
case-insensitive.<br/> ><br /> > If you want to make that change, I will not object.<p dir="ltr">If you just make
outcase insensitive that would be an improvement. Nobody sane has similar columns that differ only in case.<p
dir="ltr">Butif the original token was not quoted and the suggested token requires quoting IWBNI the hint directly
addressedthat source of confusion.<p dir="ltr">But if that gets fiddly, trying to squeeze too much in one hint then
betterthe generic hint then nothing at all. I don't want to kill a good simple change with bike shedding here 

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Column mis-spelling hints vs case folding
Next
From: Andres Freund
Date:
Subject: Re: Replication identifiers, take 4