Re: JDBC 2.0 Compatibility?

Thanks. I guess part of my question is about how these features are
implemented.

E.g. I tested scrollable result sets with the 7.3.4 driver, and I got the
feeling it's implemented by reading all rows into memory first... which
would negate some of the benefits. I thought it would behave more kind of
like LIMIT OFFSET, bringing back pages of data when needed. Did I do
something wrong or is this expected behavior?

Same with batch updates (which I didn't test) : they can be emulated by the
driver, with no performance benefits, or they can be  implemented "for
real". Same with prepared statements.

Maybe what I'm after is a performance document specifically for the PG JDBC
driver.



----- Original Message -----
From: "Dave Cramer" <pg@fastcrypt.com>
To: "Renaud Waldura" <renaud+pgsql@waldura.com>
Cc: <pgsql-jdbc@postgresql.org>
Sent: Monday, November 03, 2003 10:46 AM
Subject: Re: [JDBC] JDBC 2.0 Compatibility?


> Not sure if there is a page but to answer your question
>  Yes to all
>
> Dave
>
> On Mon, 2003-11-03 at 13:05, Renaud Waldura wrote:
> > Is there a document somewhere that describes the level of conformance of
the
> > PostgreSQL JDBC driver? Specifically, I'd like to know if/how the more
> > advanced features of JDBC are implemented -- e.g. scrollable/updatable
> > result sets, fetchSize, prepared statements, batch updates, etc.
> >
> > I guess some of these features can only be correctly implemented by the
JDBC
> > driver if the underlying database connector supports them. Is that
> > documented? I'm using PG 7.3. I already went through the manual, maybe
I've
> > missed it?
> >
> > Thanks for any pointers!
> >
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
> >
> >                http://archives.postgresql.org
> >
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
>