Re: updatable cursors and ORDER BY

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: updatable cursors and ORDER BY
Date: 2018-05-10 16:55:23
Message-ID: 22649.1525971323@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> I think that last part isn't actually written down anywhere. (It only
> states the converse.) How about a clarification like this:

> @@ -271,7 +271,10 @@ <title id="sql-declare-notes-title">Notes</title>
> and not use grouping or <literal>ORDER BY</literal>). Cursors
> that are not simply updatable might work, or might not, depending on plan
> choice details; so in the worst case, an application might work in testing
> - and then fail in production.
> + and then fail in production. If <literal>FOR UPDATE</literal> is
> + specified, then the cursor is guaranteed to be updatable, or the
> + <command>DECLARE</command> command will error if an updatable cursor
> + cannot be created for the supplied query.
> </para>

OK by me, except we don't usually use "error" as a verb. Either "fail"
or "throw an error" would read better IMO. Or you could just stop with
"guaranteed to be updatable"; I don't think the rest adds much.

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Eugene Wang 2018-05-10 19:04:35 Re: Mistakes between an example and its description
Previous Message Peter Eisentraut 2018-05-10 16:48:42 Re: updatable cursors and ORDER BY