Re: proposal: alternative psql commands quit and exit
| От | Avinash Kumar |
|---|---|
| Тема | Re: proposal: alternative psql commands quit and exit |
| Дата | |
| Msg-id | CAN0TujePiq8qo8e1HdBTGb5HMt795h=s2CDmghSveK4HBUGe7g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: proposal: alternative psql commands quit and exit ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Ответы |
Re: proposal: alternative psql commands quit and exit
|
| Список | pgsql-hackers |
It takes a few hours to learn PostgreSQL and 1 second to remember, how to quit from psql.
Surprised to see the depth of discussion on this.
He knows about psql because he searched it somewhere. Just a psql --help (anybody uses help), should help me know much more about psql.
I think its good to talk about or help with more features that helps a production database.
It takes sometime for a person to explore or know about PostgreSQL and install it.
Likewise, it takes him some more time to understand that there exists a "psql" to connect to it. I think many people doesn't find it difficult to quit using \q.
On Tue, Dec 12, 2017 at 11:19 AM, David G. Johnston <david.g.johnston@gmail.com> wrote:
I don't think this is a significant stumbling block for users adopting postgres.The OP complained, and I tend to agree, that 90% of the world uses the command "exit" to end a program and that it would be nice if we did as well. This is not just a new user consideration - and I'd say that making it so help/quit/exit/\q on a line of their own is helpfully reported to the user as having been ineffective if in the middle of a string or statement-continuation, would benefit more than just new users as well.David J.
--
9000799060
В списке pgsql-hackers по дате отправления: