From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | fgschwindt(at)qnx(dot)com, PostgreSQL-development <hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Re: your mail |
Date: | 1998-03-10 03:01:22 |
Message-ID: | 3504AD02.12001E3A@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > It would be a good idea, IMHO, that if psql is called alone (without
> > database nor any parameter), instead of try to connect to database 'user'
> > starts interactively without connection. Then, simple calling "\c dbname"
> > would connect the user to the desired database. What you think?
> > Cheers,
>
> This seems like a good idea. Any comments?
Of course :) I personally like the current default behavior, and I think that
some others find it similarly convenient. If the alternate behavior is
desirable for some, how about implementing a command line switch which would
change the default behavior to "don't open anything". Then, you can alias the
definition of psql to get what you want.
I actually had a patch of some sort which changed the behavior of "\c
unknownDB"; at the moment if a connection fails psql bails out. The patch left
the psql session open and connected to the previous database. That behavior
would be dangerous in some cases so we didn't apply it; going to an
"unconnected state" would be more helpful and less dangerous.
- Tom
From | Date | Subject | |
---|---|---|---|
Next Message | 박귀태 | 1998-03-10 03:30:56 | |
Previous Message | Bruce Momjian | 1998-03-10 03:01:17 | Re: [HACKERS] Heh, the disappearing problem! |