Hi Lothar,
I don't have any experience using the libpqxx API but I have used the libpq
API and I have found that writable cursors can be implemented in it without
too much trouble.
The PostgreSQL server does not support writable cursors (see the SQL
statement 'declare') so you will need to implement those yourself.
I would choose to use libpq rather than some other API that is not
distributed with the server. The reason is that it is more likely to remain
supported/stable than some other API (such as psqlodbc).
If you haven't seen it already, there is an object-oriented interface based
on the libpq API, SourcePro(TM) DB PostgreSQL Access Module, which supports
writable cursors (and most everything else). It is available from Rogue Wave
Software at:
http://www.roguewave.com/products/sourcepro/db/
========================
Janet Borschowa
Software Engineer, Database Products
Rogue Wave Software, a QUOVADX(tm) Division
http://www.roguewave.com
> -----Original Message-----
> From: Lothar Behrens [mailto:lothar.behrens@lollisoft.de]
> Sent: Thursday, September 16, 2004 11:03 AM
> To: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] ODBC SQLSetPos Delete problem
>
>
> Hi,
>
> I have another question:
>
> As seen, there is a libpqxx library. This is a C++ library
> following the STL and it also supports 'cursors' in another way.
>
> Would it be a good idea to write a wrapper around it to
> support my class interfaces ?
>
> Lothar
> ---- My home: www.lollisoft.de -----------------------------
> Lothar Behrens | Independent: lothar.behrens@gmx.de
> Rosmarinstr 3 | My public project:
> 40235 Düsseldorf | http://sourceforge.net/projects/lbdmf
> | -> Need comments, please visit :-)
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
http://archives.postgresql.org