Peter Eisentraut wrote:
(B> Dave Page writes:
(B> > Well what I *really* need has been made quite clear in other
(B> > posts, but, when I say resultset in the same sentence as
(B> > pgAdmin, I'm referring to the ability to enter an arbitrary
(B> > SQL query, have the results displayed in a grid, which can
(B> > then be editted. To do this pgAdmin needs to be able to
(B> > figure out enough info about the source of the data to generate
(B> > the required insert/update/delete statements.
(B> Right. But since you can't really write a literal SQL statement
(B> that does an update that refers to a previous query, you are
(B> already doing a fair amount of internal magic anyway, so if the
(B> meta-data is determined by magic as well, that seems consistent.
(BPsqlodbc driver has to parse the queries in order to
(Bimplement driver side updatable cursors unwillingly.
(BI'm very suspicios if it should be the driver's job
(Bbecause it's very hard and ineffective to parse and
(Banalyze the queries in the same way as the backend does.
(B> What you need is an updateable cursor on the server side.
(B> It has all the facilities you need,
(BReally ? How did you confirm it ?
(B> including standardized ways to find out the
(B> updatability metadata. Please concentrate on that and do not attempt to
(B> clutter the wire protocol with data that will not withstand a throrough
(B> investigation of semantics.
(B---------------------------(end of broadcast)---------------------------
(BTIP 5: Have you checked our extensive FAQ?