From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgreSQL(dot)org>, <pgsql-admin(at)postgreSQL(dot)org> |
Subject: | Re: \connect case-folding change maybe not such a good idea |
Date: | 2002-02-22 01:21:57 |
Message-ID: | Pine.LNX.4.30.0202212021380.683-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Tom Lane writes:
> I said:
> > I think the wisest course may be to revert to the 7.1 \connect behavior
>
> There is another possibility, which is to migrate to the new behavior
> over time. I like having pg_dump quote the names in \connect, because
> that gives us a shot at working with names that have embedded spaces.
> We could leave pg_dump as it stands in CVS tip, and modify psql to
> work as follows:
> 1. Quoted names in \connect are taken as quoted identifiers.
> 2. Unquoted names are taken literally (not downcased).
> Point 2 would allow forwards compatibility of existing dump files,
> while point 1 makes the new pg_dump behavior work. After a release
> or two we could migrate to regular SQL-identifier handling in \connect.
Fine with me.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2002-02-22 02:06:27 | Re: About groups in postgres |
Previous Message | Tom Lane | 2002-02-22 00:30:11 | Re: psql error |
From | Date | Subject | |
---|---|---|---|
Next Message | SAKAIDA Masaaki | 2002-02-22 02:16:14 | Re: pgbash-2.4 released |
Previous Message | Peter Eisentraut | 2002-02-22 01:19:29 | Re: SET NULL / SET NOT NULL |