> Garfield Lewis mailto:garfield.le...@lzlabs.com>>
> wrote:
> This is not a fork… it is pure Postgres 14 with an extension that checks for
> a certain environment and reports a NOTICE otherwise.
Oops, said extension meant trigger…
--
Regards,
Garfield A. Lewis
> Adrian Klaver mailto:adrian.kla...@aklaver.com>>
> wrote:
> This:
> psql:curs.pgs:2: NOTICE: DDL was performed without updating catalog
> tables: Note that CREATE TABLE from a non-SDM client does not maintain
> LzRelational catalog tables
> seems to indicate you are using some sort of Post
Garfield Lewis writes:
> DECLARE cur0 SCROLL CURSOR FOR SELECT * FROM t0 FOR UPDATE;
> psql:curs.pgs:4: ERROR: DECLARE SCROLL CURSOR ... FOR UPDATE is not supported
> DETAIL: Scrollable cursors must be READ ONLY.
Ah. Yeah, I don't think anyone is contemplating changing that.
Scrollable cursors
On 4/24/23 08:25, Garfield Lewis wrote:
Tom Lane writes:
> Doesn't that work already?
Hi Tom,
[sysprog@nucky workspace] (h-master-LZRDB-5220-fix-WCOC-failure)*$ psql -V
psql (PostgreSQL) 14.7
Is this allowed maybe in Postgres 15?
This:
psql:curs.pgs:2: NOTICE: DDL was performed wit
Tom Lane writes:
> Doesn't that work already?
Hi Tom,
This works perfectly well for a NON-UPDATABLE cursor:
[lzsystem@nucky LZRDB-5220] $ psql -U lzpgsupr -d wdbs -f curs.pgs -e
BEGIN;
BEGIN
CREATE TABLE t0(c0 int);
psql:curs.pgs:2: NOTICE: DDL was performed without updating catalog table
Garfield Lewis writes:
> Im not sure where to ask the question so Ill start here. Does anyone know
> if Postgres has any plans to support statements like FETCH/MOVE in the
> non-forward direction for SCROLLABLE/UPDATABLE cursors?
Doesn't that work already?
regards, to
Hi All,
I’m not sure where to ask the question so I’ll start here. Does anyone know if
Postgres has any plans to support statements like FETCH/MOVE in the non-forward
direction for SCROLLABLE/UPDATABLE cursors?
--
Regards,
Garfield A. Lewis
