From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | ken(at)kensystem(dot)com |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-sql(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [SQL] Case Preservation disregarding case |
Date: | 2006-12-02 13:35:56 |
Message-ID: | 20061202133556.GC26365@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
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,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Johanson | 2006-12-02 15:21:08 | Re: [HACKERS] Case Preservation disregarding case |
Previous Message | Martijn van Oosterhout | 2006-12-02 13:31:32 | Re: PostgreSQL win32 fragmentation issue |
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Johanson | 2006-12-02 15:21:08 | Re: [HACKERS] Case Preservation disregarding case |
Previous Message | Ken Johanson | 2006-12-02 07:41:37 | Re: [HACKERS] Case Preservation disregarding case |