From: Josh Berkus <josh@agliodbs.com>
To: pgsql-hackers@postgresql.org
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: FAST PostgreSQL <fastpgs@fast.fujitsu.com.au>
Subject: Re: Updatable cursor doubt
Date: Tue, 4 Sep 2007 17:37:07 -0700
Message-ID: <200709041737.09541.josh@agliodbs.com> (raw)
In-Reply-To: <46DD226F.7060602@enterprisedb.com>
References: <46DCB86F.9070102@fast.fujitsu.com.au>
<46DD226F.7060602@enterprisedb.com>
Heikki,
> FOR READ ONLY is actually part of the SELECT syntax. It's been accepted
> for at least down to version 7.4, probably even longer than that, but it
> hasn't been documented. It's accepted for the sake of compatibility with
> other DBMSs (and SQL standard?), it doesn't do anything in PostgreSQL.
>
> Now, whether we should make an effort to not allow updating a cursor on
> a query with FOR READ ONLY, that's another question. I don't think it's
> worth the effort, and it wouldn't really gain us anything. We probably
> should mention it in the manual, in the Compatibility section of SELECT
> reference page.
Who are we, MySQL? We ought not to accept the syntax if we're not going
to enforce it.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: josh@agliodbs.com, heikki@enterprisedb.com, fastpgs@fast.fujitsu.com.au
Subject: Re: Updatable cursor doubt
In-Reply-To: <200709041737.09541.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox