From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: case sensitivity for tables, columns, and constraint names
Date: Tue, 11 Dec 2007 12:30:37 -0500
Message-ID: <20071211173037.GL27409@crankycanuck.ca> (raw)
In-Reply-To: <863ECFDF04C8804ABDF3559D87F157C638E5D9@MAGPTCPEXC02.na.mag-ias.net>
References: <863ECFDF04C8804ABDF3559D87F157C638E5D9@MAGPTCPEXC02.na.mag-ias.net>
On Tue, Dec 11, 2007 at 11:05:25AM -0600, Ertel, Steve wrote:
> is wrapped in quotes. Is there a setting to allow upper case and mixed
> case names for database tables, fields, etc, without having to wrap each
> in quotes?
No, sorry. The always-one-case rule for unquoted identifiers is ANSI
conformant. As it happens, the ANSI rule also makes everything ALLCAPS, but
PostgreSQL doesn't go that way (for historical reasons).
A
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: case sensitivity for tables, columns, and constraint names
In-Reply-To: <20071211173037.GL27409@crankycanuck.ca>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox