Well said! The odds of my company looking at Village or Town as a possible
utility for tool developers has dropped to nil; I'll spend a day or two and
write it myself. I'll call it City.
Ted Neward wrote:
> >> 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.
> >
> What, to keep technical support costs down?
>
> >>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.
> >
> Your "solution" (which hasn't been proven as a solution except by your
> assertion that it is one, backed by one's willingness to (a) take your word
> for it, or (b) hunt through your source code to prove you wrong, neither of
> which is very appealing, given your written attitude) doesn't provide a
> *before-I-walk-through-the-entire-dataset* count of all rows.
>
> >> 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.
> >
> Or, one is working with a large dataset, and the idiot is the one who
> hasn't. This can also happen with large table-joins in a star schema; in the
> "real world", developers don't always have complete control over the
> database design, and have to deal with doing really large joins to get back
> the data they require.
>
> Bluntly, don't judge another developer's decisions until you understand the
> complete context in which that decision was reached. To do otherwise only
> underscores your arrogance and ultimately proves your shortcomings far
> faster than it does your experience.
>
> >Please take a look at my source code for exactly how fetchRecords() works.
> >
> Why? If you can't take the time to explain it, I'm sure as hell not going to
> bother reading it. I've got better things to do with my time.
>
> >-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
>
> Ted Neward
> Patterns/C++/Java/CORBA/EJB/COM-DCOM spoken here
> http://www.javageeks.com/~tneward
> "I don't even speak for myself; my wife won't let me." --Me
>
> ___________________________________________________________________________
> 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
