Re: bugs in Query tool... case sensitivity conflict with the rest of PgAdmin created object... explicit schema required

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: <bill(at)williamrosmus(dot)com>
Cc: <pgadmin-support(at)postgresql(dot)org>
Subject: Re: bugs in Query tool... case sensitivity conflict with the rest of PgAdmin created object... explicit schema required
Date: 2005-11-30 08:26:05
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7E4BE@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

> -----Original Message-----
> From: BillR [mailto:bill(at)williamrosmus(dot)com]
> Sent: 29 November 2005 20:50
> To: Dave Page
> Subject: Re: [pgadmin-support] bugs in Query tool... case
> sensitivity conflict with the rest of PgAdmin created
> object... explicit schema required
>
> Hi Dave,
> from my scenario, what I saw is that the Query tool is
> changing names
> to lower case. For example, in the DDL I typed in the Query tool:
> create table WorkSchema.PERSON ... not all lower case.

No, PostgreSQL folds all unquoted identifiers to lower case, not
pgAdmin. The query you enter in pgAdmin (which would need to be CREATE
TABLE "WorkSchema"."PERSON"...) is exactly what you would need to enter
in psql or any other application you might use.

The dialogues shield you from all the SQL so you don't need to know
about the quoting. If you're writing raw SQL queries though, it is
expected that you know the syntax and semantics offered by the server.

See
http://www.postgresql.org/docs/8.1/static/sql-syntax.html#SQL-SYNTAX-IDE
NTIFIERS for details.

Regards, Dave.

Browse pgadmin-support by date

  From Date Subject
Next Message Harald Armin Massa 2005-11-30 14:57:57 enhancement request: add drop cascade to columns
Previous Message Dave Page 2005-11-29 08:25:23 Re: bugs in Query tool... case sensitivity conflict with the rest of PgAdmin created object... explicit schema required