From: Dennis Bjorklund <db@zigo.dhs.org>
To: ken@kensystem.com
Cc: Martijn van Oosterhout <kleptog@svana.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: [HACKERS] Case Preservation disregarding case
Date: Sat, 02 Dec 2006 18:10:42 +0100
Message-ID: <4571B392.6020303@zigo.dhs.org> (raw)
In-Reply-To: <4571AE66.7050304@kensystem.com>
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>
<20061202133556.GC26365@svana.org>
<457199E4.3010401@kensystem.com>
<4571A3AF.6070608@zigo.dhs.org>
<4571AE66.7050304@kensystem.com>
Ken Johanson skrev:
> Although, since I'm using pgAdmin (III) to design tables in this case,
> or creating the tables through JDBC (a convenient way to copy tables and
> data from another datasource) (using the copy-paste gesture), I believe
> those tools both *are* quoting identifiers that have camel case. And
> that their behavior can't be overridden.
I know nothing about JDBC but I've heard that pgAdmin always quote
identifiers. What you can do is to always create tables and columns
using lower case in pgadmin and then you can refer to them using any
case in your SQL (as long as you don't "Quote" the identifiers in your
SQL code).
> other users may not be. And having to recreate and issue the DDL to use
> un-quoted col names will be tedious in my case since I have ~20 tables
> to import.
Yes, it will be some work but it is at least possible to do a bunch of
renames.
> So my vote would remain for having a config-option to ignore case, even
> on quoted identifiers..
And my vote is to not have such an option. But I'm not the one who
decide so don't worry about what I think :-) I would like to have an
option to upper case the identifiers instead of lower casing them as pg
do. The sql standard say that they should be upper cased. But as far as
I know there are no plan at the moment to add such an option either.
Some time in the future I expect it to be implemented only because it's
the standard.
/Dennis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: db@zigo.dhs.org, ken@kensystem.com, kleptog@svana.org
Subject: Re: [HACKERS] Case Preservation disregarding case
In-Reply-To: <4571B392.6020303@zigo.dhs.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox