| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Uppercase tab completion keywords in psql? |
| Date: | 2012-03-30 17:16:59 |
| Message-ID: | 1333127819.9045.3.camel@vanquo.pezone.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On fre, 2012-03-23 at 07:52 -0700, David Fetter wrote:
> On Thu, Mar 22, 2012 at 06:05:30PM -0400, Andrew Dunstan wrote:
> > On 03/22/2012 05:49 PM, Bruce Momjian wrote:
> > >Robert Haas and I are disappointed by this change. I liked the
> > >fact that I could post nice-looking SQL queries without having to
> > >use my capslock key (which I use as a second control key). Any
> > >chance of reverting this change?
> > >
> >
> > Should it be governed by a setting?
>
> Something like (upper|lower|preserve) ?
How about this patch then? (There are actually four possible settings,
see patch.)
| Attachment | Content-Type | Size |
|---|---|---|
| psql-comp-keyword-case.patch | text/x-patch | 4.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Roest | 2012-03-30 17:17:06 | Re: pg_dump incredibly slow dumping a single schema from a large db |
| Previous Message | Mike Roest | 2012-03-30 16:40:44 | Re: pg_dump incredibly slow dumping a single schema from a large db |