Hi,
It looks like most of the hard yards will be in getting some form of
consensus about what should be done for this TODO. I can't see a reason
not to get started on the design now. If a decision is not able to be
made after 4 years since the original discussion, is it worth removing
the
Russell Smith [EMAIL PROTECTED] writes:
The options I thought of were:
...
3. fully case sensitive even for unquoted identifiers (not spec
compliant at all, but nevertheless possibly attractive especially for
people migrating from MS SQLServer, where it is an option, IIRC).
Actually, I
On Fri, Mar 28, 2008 at 03:30:21AM +1100, Russell Smith wrote:
3. the client needs to know what quote rules are in place. (libpq:
PQfname, PQfnumber)
The question I want to see answered, is how something like DBD::Pg will
handle this. If I wrote code like this in Perl:
my %hash =
Martijn van Oosterhout [EMAIL PROTECTED] writes:
On Fri, Mar 28, 2008 at 03:30:21AM +1100, Russell Smith wrote:
3. the client needs to know what quote rules are in place. (libpq:
PQfname, PQfnumber)
The question I want to see answered, is how something like DBD::Pg will
handle this. If I
Gregory Stark [EMAIL PROTECTED] writes:
Martijn van Oosterhout [EMAIL PROTECTED] 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
Tom Lane wrote:
Russell Smith [EMAIL PROTECTED] writes:
As an attempt at a first PostgreSQL patch, I'd like to see if I can do
anything about this issue.
Trying that as a first patch is a recipe for failure... the short answer
is that no one can think of a solution that will be
Russell Smith wrote:
Tom Lane wrote:
Russell Smith [EMAIL PROTECTED] writes:
As an attempt at a first PostgreSQL patch, I'd like to see if I can
do anything about this issue.
Trying that as a first patch is a recipe for failure... the short answer
is that no one can think of a
Russell Smith [EMAIL PROTECTED] writes:
What makes this change particularly challenging? The fact that nobody
has agreed on how it should work, or the actual coding?
Getting the right design is definitely challenging. The coding might or
might not be, depending on your design ...
Hi,
As an attempt at a first PostgreSQL patch, I'd like to see if I can do
anything about this issue.
I've read both the attached threads;
http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php
http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php
There seems no
Russell Smith wrote:
The 2004 thread suggests that we want a per database setting. I am
unable to see how we share shared relations between databases with
different case folder.
pg_user is an example of this;
Lowercase database; CREATE ROLE mrruss LOGIN; results in - mrruss
as data
Russell Smith [EMAIL PROTECTED] writes:
As an attempt at a first PostgreSQL patch, I'd like to see if I can do
anything about this issue.
Trying that as a first patch is a recipe for failure... the short answer
is that no one can think of a solution that will be generally acceptable.
11 matches
Mail list logo
