Geert Van Damme wrote:
> yep, we faced the same problem :-)
> And I'm trying to do exactly what you describe. Build a library with
> resultset caching (an vector of vectors of Objects or something like it).
> One great thing about it is that caching becomes very easy.
> Dynamically creating update/insert statements, handling null values,
> date-string and back conversion ... are some of the more tricky items.
>
You might want to look at the CachedRowSet implementation (early access available
at JavaSoft's web site) for an approach to this that uses the new javax.sql
standard extension API.
One reason to do result set caching yourself (even if you had scrollable ResultSet
implementations) is that you want to be able to close the ResultSet, and the
associated Statement, so that you can give your Connection back to a connection
pool. Otherwise, you are leaving database resources occupied in between requests
from the user (who might just decide to go to lunch in between requests).
>
> Geert 'Darling' Van Damme
>
Craig McClanahan
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
