Received: from localhost (maia-2.hub.org [200.46.204.187])
	by postgresql.org (Postfix) with ESMTP id 3A8459FA136;
	Sat,  2 Dec 2006 09:36:09 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024)
	with ESMTP id 23705-06; Sat,  2 Dec 2006 09:35:59 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from svana.org (unknown [125.62.87.134])
	by postgresql.org (Postfix) with ESMTP id 7E9789F9FDA;
	Sat,  2 Dec 2006 09:36:04 -0400 (AST)
Received: from kleptog by svana.org with local (Exim 4.50)
	id 1GqV24-00071I-92; Sun, 03 Dec 2006 00:35:56 +1100
Date: Sat, 2 Dec 2006 14:35:56 +0100
From: Martijn van Oosterhout <kleptog@svana.org>
To: ken@kensystem.com
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-sql@postgresql.org,
	pgsql-hackers@postgresql.org
Subject: Re: [SQL] Case Preservation disregarding case
Message-ID: <20061202133556.GC26365@svana.org>
Reply-To: Martijn van Oosterhout <kleptog@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>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="9Ek0hoCL9XbhcSqy"
Content-Disposition: inline
In-Reply-To: <45712E31.1030004@kensystem.com>
X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6
X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522  48A7 6394 F08A 0DC6 7BE6
X-PGP-Key-URL: <http://svana.org/kleptog/0DC67BE6.pgp.asc>
User-Agent: Mutt/1.5.9i
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: kleptog@svana.org
X-SA-Exim-Scanned: No (on svana.org); SAEximRunCond expanded to false
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200612/61
X-Sequence-Number: 94542


--9Ek0hoCL9XbhcSqy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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=20
> could/should be a config option -- either globally for the server,=20
> database, or at the connection/session level. Other databases *do*=20
> support this type of granular config of misc SQL behavior -- its=20
> essential for shared hosting environments. Without it some users just=20
> *cant* make the switch. Quoting all an app's identifiers -- or renaming=
=20
> 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,
--=20
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to l=
itigate.

--9Ek0hoCL9XbhcSqy
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFcYE8IB7bNG8LQkwRAgpqAJ0bpJ3rR+2mvzIUcRRms0q5HVXBVQCeJpAE
0EHAhzv+4hXn3fKuEfUa5uc=
=51jD
-----END PGP SIGNATURE-----

--9Ek0hoCL9XbhcSqy--