Not to mention a system where 100 people are making queries at the same time.
Even if they each read in a modest sized report, multiply that times 100 and you
have memory problems. And if you don't blow out heap space, you sure as heck are
impacting performance.
Chris Pratt wrote:
> Well then call me a monumental idiot, since our database contains 180,000
> user records and on occasion we have to query them all. If Village actually
> tries to read them into a Hashtable or Vector that will blow out the Heap
> big time. Instead of making people download and read through your source
> code, why don't you provide some simple answers to questions posed here on
> the list. Most people won't take the time to read every line of source code
> for every "open source" solution available on the web to find out which is
> the best, they want answers to specific questions like this one so that they
> can decide.
> (*Chris*)
>
> ----- Original Message -----
> From: jon * <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, June 28, 1999 3:53 PM
> Subject: Re: Number of rows a query retrieved?
>
> > > Presumably, "qds.fetchRecords()" returns what -- a Vector of Hashtables
> (or
> > > Village objects) or something?
> >
> > Go look at the source code. It is there for a reason.
> >
> > >That's the same thing as calling ResultSet.next()
> > > until the ResultSet is exhausted, so that doesn't solve his problem.
> >
> > Wow, you like to argue. His problem was that he didn't know how many rows
> > were being returned. My solution does solve his problem because it tells
> you
> > how many rows were being returned.
> >
> > > Plus, what
> > > if this is going to be a monumental number of records that is apt to
> blow out
> > > memory? Do you have a way to iterate through the ResultSet?
> >
> > If one is returning a monumental number of records that can blow out the
> > amount of available memory, then, bluntly, one is an idiot.
> >
> > Please take a look at my source code for exactly how fetchRecords() works.
> >
> > -jon
> >
> >
> ___________________________________________________________________________
> > 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
> >
>
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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
