Re: BUG #5286: pgAdmin will put table and field names in apostrophes which then must be used for accessing them - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #5286: pgAdmin will put table and field names in apostrophes which then must be used for accessing them
Date
Msg-id 603c8f071001180716w15c14f78u2e496ff3222eaabc@mail.gmail.com
Whole thread Raw
In response to BUG #5286: pgAdmin will put table and field names in apostrophes which then must be used for accessing them  ("G.Schaeffler" <scgn@sie.at>)
List pgsql-bugs
On Mon, Jan 18, 2010 at 6:03 AM, G.Schaeffler <scgn@sie.at> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A05286
> Logged by: =A0 =A0 =A0 =A0 =A0G.Schaeffler
> Email address: =A0 =A0 =A0scgn@sie.at
> PostgreSQL version: 8.4.2
> Operating system: =A0 windows server 2003 std
> Description: =A0 =A0 =A0 =A0pgAdmin will put table and field names in apo=
strophes
> which then must be used for accessing them
> Details:
>
> if i create a table by using the pgadmin gui, it will create statements
> like
> CREATE TABLE "t_test" (
> id integer,
> "val" character varying(1000) NOT NULL );
> after creation, i can only access the table again if i wrap the apostroph=
es
> around the table and field names as in the create table statement.
>
> ie.
> SELECT * from t_test; will return ERROR: Relation t_test does not exit
> SELECT val from "t_test" will return ERROR: field val does not exist.
>
> when using the following sql statement
> select * from information_schema.tables where table_schema=3D'public' and
> table_type=3D'BASE TABLE'
> to get the tablename as it is saved in the db, it will return t_test, not
> "t_test" though.

The good news is that I don't think you've found a bug.  You're
probably making a mistake somewhere in here.  Someone else would have
surely noticed by now if what you're saying were true.  The bad news
is that I don't know what advice to give you on how to fix it.  The
further bad news is that this is not the right place for pgadmin
questions (if you reread the bug reporting form carefully, you'll
notice that pgadmin bugs are listed as one of the things not to report
here).  I think you might want to try here:

http://archives.postgresql.org/pgadmin-support/

...Robert

pgsql-bugs by date:

Previous
From: "Alpha Softwares Solutions"
Date:
Subject: Questions
Next
From: Robert Haas
Date:
Subject: Re: BUG #5284: Postgres CPU 100% and worker took too long to start; cancelled... Systemdown