| From: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Bernd Helmle" <mailings(at)oopsware(dot)de>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: psql command aliases support |
| Date: | 2008-04-03 14:11:51 |
| Message-ID: | 37ed240d0804030711v258e909cw765c0b343df36ca1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-04-03 14:14:38 | Re: [PATCHES] Re: BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data |
| Previous Message | Peter Eisentraut | 2008-04-03 14:09:45 | Re: psql command aliases support |