It's worth reading up on, if you care. The move to the new client/server protocol did add support for a number of things which were emulated in the past, like prepared statements. Not sure how much of this is reflected in JDBC code, but hopefully a good deal.
P Andrea Aime wrote: > Justin Deoliveira ha scritto: >> Andrea Aime wrote: >>> Justin Deoliveira ha scritto: >>>> Hi Andrea, >>> It really depends on the dbms. With Oracle the situation is as I >>> explained, with old Postgres jdbc driver prepared statements were fake, >>> in that the driver really built a full sql query and then sent it >>> to the server, with no preparation at all (it was just a way to support >>> ps API wise, while not really doing it on a practical level). >> So does this mean that in postgres we are paying the same price with >> prepared statements vs non-prepared statements? > > It may be, it may be not. I don't really know how things have evolved > since last time I did look into the postgres jdbc driver code, and that > happened some 2-3 years ago. -- Paul Ramsey Refractions Research http://www.refractions.net [EMAIL PROTECTED] Phone: 250-383-3022 Cell: 250-885-0632 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
