| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Terence Kearns" <terencek(at)isd(dot)canberra(dot)edu(dot)au>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
| Cc: | <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: double quoted object names |
| Date: | 2003-07-17 07:39:50 |
| Message-ID: | 03AF4E498C591348A42FC93DEA9661B844B316@mail.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
> -----Original Message-----
> From: Terence Kearns [mailto:terencek(at)isd(dot)canberra(dot)edu(dot)au]
> Sent: 17 July 2003 07:34
> To: Andreas Pflug
> Cc: Dave Page; pgadmin-support(at)postgresql(dot)org
> Subject: double quoted object names
>
>
> Andreas Pflug wrote:
> > and fooCol is not the same as "fooCol"
>
> What is the deal with this anyway? Everytime I specify an object name
> with mixed case it decides to throw double quotes around it.
It has to otherwise PostgreSQL will fold the identifier to lowercase.
> Also, I created a schema called global (no mixed case) and now
> pgAdminIII refers to all objects in this schema as "global".objectname
Global is probably a reserved word, so must be quoted if used.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Cuypers | 2003-07-17 07:40:08 | Re: changing comment for a table makes pgadmin |
| Previous Message | Terence Kearns | 2003-07-17 06:33:48 | double quoted object names |