Horton

Re: cursor sensitivity misunderstanding

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-02-25T15:37:02Z
Lists: pgsql-hackers

Attachments

On 18.02.21 19:14, Peter Eisentraut wrote:
> On 18.02.21 17:11, David G. Johnston wrote:
>> The OP was doing a course based on Oracle and was confused regarding 
>> our behavior.  The documentation failed to help me provide a useful 
>> response, so I'd agree there is something here that needs reworking if 
>> not outright fixing.
> 
> According to the piece of the standard that I posted, the sensitivity 
> behavior here is implementation-dependent (not even -defined), so both 
> implementations are correct.
> 
> But the poster was apparently also confused by the same piece of 
> documentation.

I came up with the attached patch to sort this out a bit.  It does not 
change any cursor behavior.  But the documentation now uses the terms 
more correctly and explains the differences between SQL and the 
PostgreSQL implementation better, I think.

Commits

  1. Fix use of cursor sensitivity terminology