From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] psql -e and -n flags |
Date: | 2000-02-06 16:34:40 |
Message-ID: | 389DA2A0.EC14B8D3@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> The suggestion I have is to offer the traditional behaviour with a single
> -e flag, so there's little change for anyone switching from <7.0, and the
> "full" echo mode with two -e flags. I'd then change the flags in the
> regression drivers to -e -e. Comments? Better ideas?
Hmm. imho having a *count* of switch options being significant is the
wrong way to go. It gets in the way of things like
# alias ps psql -e
# ps -e postgres
where someone has defined a "convenience" alias for everyone and
someone else uses it later. Also, it is a style of switch invocation
not appearing elsewhere afaik.
I'd suggest a switch style like "-ee" or "-eb" (backend) or "-ev"
(verbatim) or ??? Comments?
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | Karl DeBisschop | 2000-02-06 16:49:32 | Re: [HACKERS] psql -e and -n flags |
Previous Message | Don Baccus | 2000-02-06 16:03:11 | Re: [HACKERS] psql -e and -n flags |