-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, Apr 5, 2008 at 12:14 PM, Gregory Stark wrote:
> "Brendan Jurd" writes:
> > Okay, but what on earth is "\c&" and what would you expect it to do
> > when it "works"? I suppose you're connecting to a database, but
> > somehow I don't think you're talking about a database with the name
> > "&".
>
> Sorry, it was in a patch I submitted a while ago to do concurrent connections.
> It's supposed to be like & in the shell -- which doesn't require a space
> before it. I was just explaining in a parenthetical comment the only reason I
> was personally fond of that feature. It's not an important factor.
>
Ah, thanks for clearing that up. I wasn't tuned into the concurrent
connections thread.
I agree that having shell-like behaviours is a useful goal. The good
news is, if we had a psql where the command and the arguments are
always separated, we could just make \c& a separate command from \c.
Cheers,
BJ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: http://getfiregpg.org
iD8DBQFH9tbk5YBsbHkuyV0RAuohAKDYa6/hTEqVQr5nYlsZLLu14NuwzwCeOmVF
854P3drq/8+SrMwcbhUFNw4=
=PjSp
-----END PGP SIGNATURE-----
