Re: BUG #5845: Postgres does not seem to handle unquoted upper cased object identifiers - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #5845: Postgres does not seem to handle unquoted upper cased object identifiers
Date
Msg-id 1295988611-sup-1649@alvh.no-ip.org
Whole thread Raw
In response to BUG #5845: Postgres does not seem to handle unquoted upper cased object identifiers  ("Kasia Tuszynska" <ktuszynska@esri.com>)
List pgsql-bugs
Excerpts from Kasia Tuszynska's message of lun ene 24 16:48:21 -0300 2011:

> Basic issue:
> In the documentation Postgres states that it's identifiers (table, column
> names etc)are case insensitive and thus it stores everything in lower case.
> To preserve case of a identifier, the name needs to be quoted.


> But it's handing of incoming upper cased identifiers seems to be
> inconsistent.
> We have observed the following:
> create table á007 (objectid integer);
> select * from á007;Found
> select * from Á007;Not Found

Yes, this is a known limitation, but previous discussions about it
haven't led to finding a solution to the problem.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-bugs by date:

Previous
From: Josh Berkus
Date:
Subject: Multicolun index creation never completes on 9.0.1/solaris
Next
From: "Murray S. Kucherawy"
Date:
Subject: Re: BUG #5837: PQstatus() fails to report lost connection