Re: BUG #14500: error message displays "schema dot relation" in double quotes all together

Thank you for the reply!
I understand that double quotes here do not mean a relation exact name, but
rather identify the object in general.
Yet, look at this sample:

t=# select * from public."Mixed.Case";
ERROR: * relation "public.Mixed.Case" *does not exist
LINE 1: select * from public."Mixed.Case";
^

2017-01-17 15:19 GMT+00:00 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>:

> On Tue, Jan 17, 2017 at 4:09 AM, <vodevsh(at)gmail(dot)com> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 14500
>> Logged by: Vladimir Svedov
>> Email address: vodevsh(at)gmail(dot)com
>> PostgreSQL version: 9.6.1
>> Operating system: Linux
>> Description:
>>
>> Hi,
>> I'm not sure if it's a bug or feature, but I find error message
>> misleading.
>> ERROR: relation [“schema_name.table_name”] does not exist gives an
>> impression that schema name is part of relation name. Should not it be
>> ERROR: relation [“schema name”].["table_name"] does not exist instead? I
>> doubt it's a bug, because this message seems version not specific. But
>> does
>> not it look wrong?
>>
>
> ​I see the confusion but supposedly you'd have to write your alternate
> version:
>
> relation ""schema_name"."table_name"" does not exist - and the excess of
> quotes in that situation would be problematic.
>
> More to the point, the double quotes are not part of the identifiers but
> rather offset the item being named from the rest of the sentence fragment.
> ​The portion within the quotes is case-sensitive and reflects that value
> being looked up after any case-folding happens.
>
> Its definitely not a bug and doesn't seem like something that would be
> worth it to change.
>
> David J.
>
>