JDBC 2 has mechanisms to cope
with this.
Likewise Oracle lets you give a
rowcount.
If you are stuck on JDBC 1 then
you can just store unique keys
in the session, and do a query
for them as the use pages up and
down
Jake Brain <[EMAIL PROTECTED]> wrote:
__________
>Hi, there are certain queries a user may make that return many results (e.g all
>employees)
>
>My way to handle this was to put all results( large vector) in session, then allow
>the user to scroll thru results(next, previous buttons). So this means there is only
>one query rather than many.
>
>Now people r worried when to know to take it out of session to free memory, in an
>elegant way design wise. In other words if the user clicked on anything else on that
>page(links to other servlets) other than the next , previous buttons, we can assume
>there is no longer a need to have that large vector in session. But what is the
>elegant way to remove the vector in the other servlets? Just simply check for this
>object and remove it? Has anyone else had to design something like this? Thanks.
>
>___________________________________________________________________________
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff SERVLET-INTEREST".
>
>Archives: http://archives.java.sun.com/archives/servlet-interest.html
>Resources: http://java.sun.com/products/servlet/external-resources.html
>LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
http://www.westpoint.ltd.uk/
Internet reconnaissance services.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
