My apologies I sent this reply to David only by mistake.
--
--
---------- Forwarded message ---------
From: Steve Haresnape <s.haresnape@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 15 Mar 2019 at 13:09
Subject: Re: Camel case identifiers and folding
To: David G. Johnston <david.g.johnston@xxxxxxxxx>
From: Steve Haresnape <s.haresnape@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 15 Mar 2019 at 13:09
Subject: Re: Camel case identifiers and folding
To: David G. Johnston <david.g.johnston@xxxxxxxxx>
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@xxxxxxxxx> wrote:
On Thu, Mar 14, 2019 at 4:07 PM Steve Haresnape
<s.haresnape@xxxxxxxxxxxxxxxxxxxxxxx> 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.
Steve Haresnape
60 Kauri Road, Awhitu, RD 4 Waiuku 2684
Phone: (09) 235 1698
Mobile: 021 514 666
Steve Haresnape
60 Kauri Road, Awhitu, RD 4 Waiuku 2684
Phone: (09) 235 1698
Mobile: 021 514 666
