Re: psql command aliases support - Mailing list pgsql-patches

From Brendan Jurd
Subject Re: psql command aliases support
Date
Msg-id 37ed240d0804030711v258e909cw765c0b343df36ca1@mail.gmail.com
Whole thread Raw
In response to Re: psql command aliases support  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: psql command aliases support
Re: psql command aliases support
List pgsql-patches
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Am Donnerstag, 3. April 2008 schrieb Gregory Stark:
>
>  > #= \oldd
>  >
>  > #= \old
>  > #= select 'where is all my output going?'
>  > #= select 'what happened to my ldd file?'
>

psql allows you to omit the space between the command and argument?
Does anybody else find that weird?

What is the virtue of allowing such a syntax in the first place?  I
can't think of any other context where it's okay to issue a command
together with arguments without some kind of delimiter, for the
obvious reason that it introduces ambiguities such as those Greg
described.

Cheers,
BJ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: http://getfiregpg.org

iD8DBQFH9OWk5YBsbHkuyV0RAmZ4AKC9qjU+KqgLJxQSJ4sD7X4YaPEbHgCg8ipW
BRedeq4kG/FpqZBoptrKlRw=
=out8
-----END PGP SIGNATURE-----

pgsql-patches by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: psql command aliases support
Next
From: Tom Lane
Date:
Subject: Re: Re: [BUGS] BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data