Home > mailing lists

Fwd: Camel case identifiers and folding - Mailing list pgsql-general

From	Steve Haresnape
Subject	Fwd: Camel case identifiers and folding
Date	March 16, 2019 11:53:33
Msg-id	CAJrKPxd+yxM=oBtECaHpm7zrjCutQ23THV7aHOJ8LbyONJiJqQ@mail.gmail.com Whole thread Raw
In response to	Camel case identifiers and folding (Steve Haresnape <s.haresnape@creativeintegrity.co.nz>)
Responses	Re: Fwd: Camel case identifiers and folding Re: Fwd: Camel case identifiers and folding
List	pgsql-general

Tree view

My apologies I sent this reply to David only by mistake.

---------- Forwarded message ---------
From: Steve Haresnape <s.haresnape@creativeintegrity.co.nz>
Date: Fri, 15 Mar 2019 at 13:09
Subject: Re: Camel case identifiers and folding
To: David G. Johnston <david.g.johnston@gmail.com>

As I said, I don't want to quote my identifiers. I know what that does. I want to specify them in a certain way, see them in that same way, but refer to them in any old way.

You can call it normalize or fold or whatever. It's a bad design choice, and not even a completely compliant choice.

Is a cure contemplated? I know it's not just me that dislikes this.

On Fri, 15 Mar 2019 at 12:21, David G. Johnston <david.g.johnston@gmail.com> wrote:

On Thu, Mar 14, 2019 at 4:07 PM Steve Haresnape
<s.haresnape@creativeintegrity.co.nz> wrote:
>
> I'm porting a sql server database to postgresql 9.6. My camelCase identifiers are having their humps removed. This is disconcerting and sad.
>
> Is there a cure for this?

No

>I don't want to quote my identifiers unless I have to.

PostgreSQL made the choice long ago to normalize unquoted identifiers
to lower case. Quoting them will preserve whatever you type,
including case.

David J.