I think jon star is upset about something. Very argumentative. If I had the time
to read his source, I would, but quite honestly I think he's got an attitude
problem which doesn't bode well for support!
I'm sure that Village and Town are perfectly viable solutions for developers
that have zero sql abilities (although, in actuality, his tools could cause vast
problems with large tables and unchecked key criteria).
But the original question was how to convert existing SQL into something that
could be used without the single-quotes. And since the coder has already taken
the time to create SQL, why convert it to Village/Town? A few simple changes to
his existing code, without having to create keyDefs() or whatever the other
stuff was, basically without even having to learn another toolset, he can use
prepared statements.
And to assume that all queries are going to return a few rows -- well, that's
just shortsighted.
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
