Re: [HACKERS] Re: [GENERAL] Variable case database names

From: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, prlw1(at)cam(dot)ac(dot)uk, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Re: [GENERAL] Variable case database names
Date: 2000-01-21 19:06:59
Message-ID: 20000121190659.D18047@quartz.newn.cam.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Thu, Jan 20, 2000 at 05:04:45PM -0500, Bruce Momjian wrote:
> [Charset ISO-8859-1 unsupported, filtering to ASCII...]
> > There is some code in libpq which converts all database names to
> > lower-case, unless it's double quoted. That seems a little ill-conceived
> > to me, since you'd actually have to pass it something like
> > PGconnectdb("dbname=\"Newnham\"");
> >
> > If anything, this would make it inconvenient it psql, because you'd have
> > to write
> > \c '"Newnham"'
> > since
> > \c "Newnham"
> > is interpreted differently.
> >
> > Does anyone have an explanation for this? Why not leave the name as is?
>
> We do the same thing with queries, right? We force identifiers to lower
> case unless quoted.

The point was: the database name was quoted. I didn't think to quote it
a second time. (single quoting for the create was sufficient, and the export
from access didn't mind about the case)

Cheers,

Patrick

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Brian Moon 2000-01-21 21:11:08 Not enough connections on Solaris
Previous Message Ed Bras 2000-01-21 18:47:07 RE: stat failed on /usr/lib/pgsql/plpgsql.so; no file or directory

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Samersoff 2000-01-21 19:48:50 Re: [HACKERS] Re: vacuum timings
Previous Message Tom Lane 2000-01-21 19:06:31 Re: vacuum timings