pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ken Johanson <pg-user@kensystem.com>
To: Martijn van Oosterhout <kleptog@svana.org>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Case Preservation disregarding case
Date: Sat, 02 Dec 2006 08:21:08 -0700
Message-ID: <457199E4.3010401@kensystem.com> (raw)
In-Reply-To: <20061202133556.GC26365@svana.org>
References: <200610271623.37525.beauh@bluefrogmobile.com>
	<1162003132.687.8.camel@pampa>
	<200610301928.51255.beauh@bluefrogmobile.com>
	<23177.1162265010@sss.pgh.pa.us>
	<EB48EBF3B239E948AC1E3F3780CF8F88012F88DD@MI8NYCMAIL02.Mi8.com>
	<45712E31.1030004@kensystem.com>
	<20061202133556.GC26365@svana.org>

Martijn van Oosterhout wrote:
> On Sat, Dec 02, 2006 at 12:41:37AM -0700, Ken Johanson wrote:
>> 1: It seems like this behavior of case sensitive-or-not-identifiers 
>> could/should be a config option -- either globally for the server, 
>> database, or at the connection/session level. Other databases *do* 
>> support this type of granular config of misc SQL behavior -- its 
>> essential for shared hosting environments. Without it some users just 
>> *cant* make the switch. Quoting all an app's identifiers -- or renaming 
>> camel-case to underscored -- show stopper.
> 
> What about option 3: use camelcase without underscares and don't quote.
> Then you get case-insensetivity and it's still readable.
> 
> You're obviously talking about an app which isn't quoting identifiers,
> so I'm not sure what the actual problem is.
> 
> Have a nice day,

Yes, I do routinely use non-quoted identifiers. The problem is, that 
they are case-folded (to lower in PG's case), so my camel-case does not 
match. For the query to work I MUST quote identifiers hat have camel-case.

SELECT
pers."firstName",
pers.lastname,
...

Has your experience with PG been different? If so I presume you have 
have found a config that allows?:

SELECT
pers.firstName,
pers.lastname,

Ken





view thread (29+ messages)  latest in thread

Message-ID: <457199E4.3010401@kensystem.com>
Permalink:  ../457199E4.3010401@kensystem.com/
Also on:    postgresql.org/message-id/457199E4.3010401@kensystem.com

 · 

reply

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: pg-user@kensystem.com, kleptog@svana.org, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] Case Preservation disregarding case
  In-Reply-To: <457199E4.3010401@kensystem.com>

* 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