Magnus Hagander <magnus@xxxxxxxxxxxx> writes: > On Fri, May 3, 2024 at 11:08 PM Adrian Klaver <adrian.klaver@xxxxxxxxxxx> > wrote: >> This: >> "Did not find any relation named "public.some_idIds"." >> to me indicates it did look for the properly cased name. > That is arguably a really bad error message, because it puts those quotes > there whether needed or not. if you put the quotes in there, you get: > Did not find any relation named "public."some_idIds"". This is one of the places where it's unfortunate that our English-text rule for quoting a string to set it off from the rest of the error message collides with SQL's rule for quoting an identifier. Leaving out the outer quotes would be contrary to our style guide, but having them there can be confusing too to people who know SQL well. It'd be better if we could show the transformed search string, but since it's been marked up to be a regex I fear that'd introduce even more confusion than it solves. regards, tom lane
