From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "FAST PostgreSQL" <fastpgs(at)fast(dot)fujitsu(dot)com(dot)au> |
Subject: | Re: Updatable cursor doubt |
Date: | 2007-09-05 00:37:07 |
Message-ID: | 200709041737.09541.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | korry.douglas | 2007-09-05 00:55:21 | Re: Has anyone tried out the PL/pgSQL debugger? |
Previous Message | John DeSoi | 2007-09-05 00:18:14 | Re: Has anyone tried out the PL/pgSQL debugger? |