Re: Updatable Cursors, CTID, and Views - Mailing list pgsql-odbc

From Dave Page
Subject Re: Updatable Cursors, CTID, and Views
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E41A74A5@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Updatable Cursors, CTID, and Views  ("Mark Dexter" <MDEXTER@dexterchaney.com>)
List pgsql-odbc
 


From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Mark Dexter
Sent: 27 July 2004 23:26
To: pgsql-odbc@postgresql.org
Subject: [ODBC] Updatable Cursors, CTID, and Views

From a prior posting on November 5, 2002, I found this text regarding the use of CTID in the ODBC driver:

The driver uses CTID and OID to implement updatable cursors. Please turn off the *Updatable cursors* DSN option if you don't like the behavior. regards, Hiroshi Inoue

I am having a problem where I need to use updatable cursors with views.  It appears that the ODBC driver is trying to use the CTID and OID columns and that views don't have these columns.  Is it possible to use updatable cursors with views via the PostgreSQL ODBC driver?

 Not from what Hiroshi has said (he wrote the cursor code). I imagine he used CTID because it needs to be able to locate the exact version of each row - in a view that won't work because ctid don't exist. I guess you could try adding it to your view definition though that will probably only work for single table views of course.

I'm not sure why he would have used oid given that it may not exist even in a table...

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: problem with CVS version
Next
From: Janet Borschowa
Date:
Subject: Re: Updatable Cursors, CTID, and Views