On Mon, 28 Oct 2002, Donald Ball wrote: > In any case, mind a quick question on the way the sql taglib is > implemented? Is it the case that the code iterates over the ResultSet > and pulls the data into the Result object before closing the jdbc > connection? Or does it do something more clever so that the we don't > have to pay the overhead of touching the data twice?
No, there's pretty much no way to avoid the inefficiency of caching when the goal is to let page authors avoid having to think about the open ResultSet or backing database connection. We chose simplicity over performance in this case, presuming that in most cases, the overhead wouldn't be too large except for particularly large data sets. -- Shawn Bayern "JSTL in Action" http://www.jstlbook.com -- To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
