From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Kasia Tuszynska <ktuszynska(at)esri(dot)com> |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #5845: Postgres does not seem to handle unquoted upper cased object identifiers |
Date: | 2011-01-25 20:50:57 |
Message-ID: | 1295988611-sup-1649@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-01-25 21:21:55 | Re: Multicolun index creation never completes on 9.0.1/solaris |
Previous Message | curt | 2011-01-25 20:47:53 | BUG #5848: Between operator issue |