From: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | \d failing to find uppercased object names |
Date: | 2013-01-24 12:46:09 |
Message-ID: | CANNMO++Bh1O5jXqQA_JpBfvojcVD7UtkAZQvBNHQxK_oVPn+nw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
some app created tables ussing uppercase letters in table names (this app
was migrated from mysql). One tries to use \d to search tables info:
ru=# \d pnct_Board
Did not find any relation named "pnct_Board".
Of course, it works with ":
ru=# \d "pnct_Board"
Table "public.pnct_Board"
Column | Type | Modifiers
-------------+----------+-----------------------------------------------------------
id | bigint | not null default
nextval('"pnct_Board_id_seq"'::regclass)
<...>
Could this be considered as gotcha?
The thing is that Postgres reply is pretty much clear:
> Did not find any relation named "pnct_Board".
, but table "pnct_Board" does exist in the system, so Postgres' reply is
obviously incorrect.
Version: 9.2.1
From | Date | Subject | |
---|---|---|---|
Next Message | Виктор Егоров | 2013-01-24 12:51:46 | Re: \d failing to find uppercased object names |
Previous Message | Craig Ringer | 2013-01-24 12:11:16 | Re: BUG #6510: A simple prompt is displayed using wrong charset |