From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Bernd Helmle" <mailings(at)oopsware(dot)de> |
Subject: | Re: bug in on_error_rollback !? |
Date: | 2006-10-27 16:49:34 |
Message-ID: | 200610271849.34909.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gurjeet Singh wrote:
> \ds and \dS are commands (first token on the line) so it is
> acceptable that they be case-sensitive. But a command's
> parameters/arguments should not be case sensitive, unless quoted.
This distinction has not basis in SQL syntax.
> If it is documented that psql commands are case sensitive, then I
> would like to point to an ambiguity:
If it helps, compare this to ECPG: The C parts follow the syntax rules
of C, the SQL parts follow the syntax rules of SQL. In psql, the psql
parts follow the syntax rules of psql, the SQL parts follow the syntax
rules of SQL. The syntax rules of psql in turn are inspired by Unix
shells, sort of because psql is used that way. (Surely one wouldn't
want the argument to \i be case-insensitive?)
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-10-27 16:53:52 | Re: BUG #2724: Could not check connection status with "ssl=on" |
Previous Message | Tom Lane | 2006-10-27 16:01:12 | Re: WAL logging freezing |