On Wed, 2003-03-12 at 20:45, Hiroshi Inoue wrote:
> Peter Eisentraut wrote:
> >
> > Dave Page writes:
> >
> > > Well what I *really* need has been made quite clear in other
> > > posts, but, when I say resultset in the same sentence as
> > > pgAdmin, I'm referring to the ability to enter an arbitrary
> > > SQL query, have the results displayed in a grid, which can
> > > then be editted. To do this pgAdmin needs to be able to
> > > figure out enough info about the source of the data to generate
> > > the required insert/update/delete statements.
> >
> > Right. But since you can't really write a literal SQL statement
> > that does an update that refers to a previous query, you are
> > already doing a fair amount of internal magic anyway, so if the
> > meta-data is determined by magic as well, that seems consistent.
>
> Psqlodbc driver has to parse the queries in order to
> implement driver side updatable cursors unwillingly.
> I'm very suspicios if it should be the driver's job
> because it's very hard and ineffective to parse and
> analyze the queries in the same way as the backend does.
jdbc has to do this too, and the backend is in a much better position to
do the parsing IMO as well.
>
> > What you need is an updateable cursor on the server side.
> > It has all the facilities you need,
>
> Really ? How did you confirm it ?
>
> > including standardized ways to find out the
> > updatability metadata. Please concentrate on that and do not attempt to
> > clutter the wire protocol with data that will not withstand a throrough
> > investigation of semantics.
>
> regards,
> Hiroshi Inoue
> http://www.geocities.jp/inocchichichi/psqlodbc/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
--
Dave Cramer <dave@fastcrypt.com>
Cramer Consulting
