From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Dave Page <dpage@vale-housing.co.uk>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: Roadmap for FE/BE protocol redesign
Date: Wed, 12 Mar 2003 17:02:19 +0900
Message-ID: <3E6EE98B.C9357A95@tpf.co.jp> (raw)
References: <Pine.LNX.4.44.0303120107410.1617-100000@peter.localdomain>
Peter Eisentraut wrote:
>
> Dave Page writes:
>
> > I don't know about JDBC, but ODBC could use it,
> > and it would save a heck of a lot of pain in apps
> > like pgAdmin that need to figure out if a column
> > in an arbitrary resultset might be updateable.
>
> Strictly speaking, result sets are never updatable,
> because there's no way you can refer to a result set
> and tell the system to update it.
> So let's hear what you *really* need and then consider
> interfaces for *that*. Maybe updatable views or
> updatable cursors?
The word *result set* is used variously
and *updatable cursors* has its meaning
in some middleware applications.
The word *cursor* is used variously too.
For example, ODBC cursors don't necessarily
mean(correspond to) the dbms cursors.
If there's a suitable cursor, the ODBC driver
may conveniently use it to implement ODBC
cursors. Otherwise the ODBC driver may implement
ODBC cursors by itself. PostgreSQL has paid
attention to the cursor support little and I
don't expect much of server-side cursors.
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: Inoue@tpf.co.jp, peter_e@gmx.net, dpage@vale-housing.co.uk, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
In-Reply-To: <3E6EE98B.C9357A95@tpf.co.jp>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox