> > The fault is with your program components that are insisting on upper
> > case rather than accepting either case.
>
> In defence of this unknown component, the sql specifications says that
> identifiers should be upper cased where pg do lower case.
>
> I would welcome a initdb setting that defi
Tom Lane wrote:
> I wonder though whether we could offer some tweaking on client side.
> For instance consider the JDBC driver's getMetaData operations.
> You could imagine a JDBC driver mode that would smash all returned
> identifiers to upper case.
Then again, JDBC applications can query
Databa
On Tue, 14 Sep 2004, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > ... There's been talk about supporting a
> > mode which case folds the other direction. In general, however, mixing
> > quoted and unquoted names is dangerous in all complient databases, because
> > in none would
Stephan Szabo <[EMAIL PROTECTED]> writes:
> ... There's been talk about supporting a
> mode which case folds the other direction. In general, however, mixing
> quoted and unquoted names is dangerous in all complient databases, because
> in none would "Bla" and bla or BLA be the same name.
We have
On Tue, 14 Sep 2004, Oliver Elphick wrote:
> The fault is with your program components that are insisting on upper
> case rather than accepting either case.
In defence of this unknown component, the sql specifications says that
identifiers should be upper cased where pg do lower case.
I would w
On Tue, 14 Sep 2004, Christian Sell wrote:
> Hello,
>
> I am running into a problem with PGs case sensitivity with regard to column and
> table names. I am using program components that require the object names
> returned from database metadata queries to be in uppercase. Therefore, I am
> forced
