From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SET TRANSACTION and SQL Standard |
Date: | 2009-01-09 14:45:36 |
Message-ID: | 1231512336.18005.437.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 2009-01-09 at 16:14 +0200, Peter Eisentraut wrote:
> 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;
> >
> > Unsurprisingly, these violate the SQL Standard:
> > * p.977 section 19.1 syntax (1)
> > * p.957 section 17.3 syntax (2)
>
> 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.
Except when the standard explicitly forbids it, as with the above.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-01-09 14:51:44 | Re: foreign_data test fails with non-C locale |
Previous Message | Tom Lane | 2009-01-09 14:39:49 | Re: SET TRANSACTION and SQL Standard |