Re: rationale behind quotes for camel case?

From: Andrew Sullivan <ajs(at)anvilwalrusden(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: rationale behind quotes for camel case?
Date: 2011-06-28 14:11:14
Message-ID: 20110628141113.GB4642@shinkuro.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jun 28, 2011 at 04:00:42AM -0700, John R Pierce wrote:
> capitals (probably reflecting its 1980s IBM origins), but PG decided
> a long time ago to default to lower case, since the final result has
> the same effect.

Well, it _sort of_ has the same effect. In a traditional SQL
environment, if you use TABLENAME and "TABLENAME", they're equivalent,
but tablename and "TABLENAME" are not. In PostgreSQL, that doesn't
work: tablename and "tablename" are equivalent instead. This
sometimes bites people when moving to Postgres, because their
identifier quoting hasn't been consistent in their application.

A

--
Andrew Sullivan
ajs(at)anvilwalrusden(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2011-06-28 14:40:16 Re: Gist Index: Problem getting data in GiST Support Functions "penalty".
Previous Message Merlin Moncure 2011-06-28 13:43:58 Re: rationale behind quotes for camel case?