thanks for pointing out the database resource consumption problem!
i'll probably define an upper limit for result rows shown to the user in
my application. then i'll use one query to get all the object ids of the
result objects, store them (instead of the ResultSet) in the user's
session. then the object data can be fetched from the database
"page-by-page" as the user browses through the list of result objects.
best regards,
--
aspa
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
