Re: double quoted object names - Mailing list pgadmin-support

From Terence Kearns
Subject Re: double quoted object names
Date
Msg-id 3F1662B6.2060604@cts.canberra.edu.au
Whole thread Raw
In response to Re: double quoted object names  ("Dave Page" <dpage@vale-housing.co.uk>)
Responses Re: double quoted object names  (Andreas Pflug <pgadmin@pse-consulting.de>)
List pgadmin-support
Dave Page wrote:
> It has to otherwise PostgreSQL will fold the identifier to lowercase.
> 

I prefer mixed-case multi-word identifiers rather than identifiers with 
words separated by underscors but I think I will use lowercase 
everywhere from now on :/

> 
>>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.
> 

you guessed right. I checked up on it at
http://www.postgresql.org/docs/7.3/interactive/sql-keywords-appendix.html

Doesn't seem like there are many words left in the english language that 
aren't reserved ;) I didn't realise there were so many [non-]reserved 
words. Postgres reserves GLOBAL as a "non-reserved" word as opposed to a 
"reserved" word (just read the docs from the above link).

A print out of this list now stays by my side...


-- 
Terence Kearns ~ ph: +61 2 6201 5516
IT Database/Applications Developer
Enterprise Information Systems
Client Services Division
University of Canberra
www.canberra.edu.au



pgadmin-support by date:

Previous
From: Marc Cuypers
Date:
Subject: Re: changing comment for a table makes pgadmin
Next
From: Andreas Pflug
Date:
Subject: Re: double quoted object names