From: | Brian E Gallew <geek+(at)cmu(dot)edu> |
---|---|
To: | "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Re: tab completion in psql |
Date: | 1999-11-30 18:49:24 |
Message-ID: | emacs-smtp-20280-14404-7220-662833@export.andrew.cmu.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Then Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> spoke up and said:
> The tab completion is not very smart, it only covers the really obvious
> cases. Doing FROM shouldn't be so hard, but once you get into WHERE you
> almost end up writing a complete SQL parser just for this. Not that
> there's anything fundamentally wrong with that. It's a very evolving piece
> of code, however; it can only get better. I bet those readline authors
> never had this one in mind. Otherwise readline would play nicer with it.
I've used Python's readline support, and I must say it's really nice
when the readline engine can complete more dynamic names. It would be
very nice if "\d table" or "\dt" populated a dictionary of some kind
which could then be used for completion. While context sensitivity
would be even better, it might be worthwhile to simply have a dynamic
dictionary.
--
=====================================================================
| JAVA must have been developed in the wilds of West Virginia. |
| After all, why else would it support only single inheritance?? |
=====================================================================
| Finger geek(at)cmu(dot)edu for my public key. |
=====================================================================
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 1999-11-30 19:36:01 | Re: Ownership/protection (was Re: [HACKERS] Portability) |
Previous Message | Vince Vielhaber | 1999-11-30 17:55:21 | Re: Ownership/protection (was Re: [HACKERS] Portability) |