On Mon, May 14, 2007 at 11:55:07AM -0500, Jim C. Nasby wrote: > On Mon, May 14, 2007 at 11:03:52AM -0400, Tom Lane wrote: > > Gregory Stark <[EMAIL PROTECTED]> writes: > > > But these kinds of inconsistent behaviours can be traps for users. It > > > means > > > "\c1" and "\c 1" do different things even though "\cpostgres" and \c > > > postgres" > > > do the same thing. And it means "\c1" might connect to a database named > > > "1" > > > today but switch sessions tomorrow. > > > > The real problem here is trying to overload an existing command name > > with too many different meanings. You need to pick some other name > > besides \c. > > > > If you were willing to think of it as "switch session" instead of "connect", > > then \S is available ... > > Since this command will be getting used very frequently by anyone using > concurrent connections interactively, it'd be nice if it was lower-case. > It looks like that limits us to j, k, m, n, v, and y. In unix this idea > is about jobs, what about using \j?
I suppose there is some reason the bash/csh job control characters: %- %+ %1 won't work? -dg -- David Gould [EMAIL PROTECTED] If simplicity worked, the world would be overrun with insects. ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org