Peter Eisentraut <pete...@gmx.net> writes:
> Simon Riggs wrote:
>> I notice that we allow commands such as
>> SET TRANSACTION read only read write read only;
>> BEGIN TRANSACTION read only read only read only;
> Well, we allow a lot of things. Violations of the SQL standard happen
> when a command that appears in the standard doesn't do what the standard
> says. Allowing commands that are not in the standard is not a violation.
I agree that "spec violation" is not a good argument for rejecting
these. However, self-consistency with our own common practice should
be considered. In practically every utility command we have that takes
a list of options, we throw "conflicting or redundant options" errors
in similar cases.
My own feeling is that the second example is okay but the first should
be rejected, since (a) it's quite unclear what the user wants, and (b)
the ensuing behavior would be determined by implementation artifacts
like which order we processed the options in.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
