Re: TODO Item: Consider allowing control of upper/lower case folding of unquoted, identifiers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Russell Smith" <mr-russ(at)pws(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO Item: Consider allowing control of upper/lower case folding of unquoted, identifiers
Date: 2008-03-28 00:57:20
Message-ID: 20336.1206665840@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> "Martijn van Oosterhout" <kleptog(at)svana(dot)org> writes:
>> Will this change break my code?

> Well, DBI already has to deal with this anyways because it tries to provide a
> database-independent interface. So you can instruct DBI to upcase, downcase,
> or leave the identifiers as the database provides them by setting this
> property on your database connection:

That's not a solution, that's a kluge with very obvious failure modes.

Now admittedly it's probably not *likely* that someone would use
identifiers differing only in case in a single table definition.
But it's legal, and in fact we're required by spec to support it.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2008-03-28 01:48:41 Re: pg_standby for 8.2 (with last restart point)
Previous Message Aidan Van Dyk 2008-03-27 23:53:18 Re: Status of GIT mirror (Was having problem in rsync'ing cvs)