Re: hi all

Commentary embedded.
On Oct 4, 8:51 am, Noons <wizofo..._at_yahoo.com.au> wrote:
> On Oct 3, 11:26 pm, "fitzjarr..._at_cox.net" <fitzjarr..._at_cox.net> wrote:
>
> > <cacophony snipped>
> > It appears from this:
>
> > java.sql.SQLException: Exhausted Resultset
>
> > you likely haven't gotten the first row and the pointer is sitting at
> > the on-before-first element. A next() call should fix the problem.
>
> David! You're still thinking procedurally!

But, at least I'm thinking ...I think ...

> What he needs is an iterator class with polymorphic
> capability, so that he can very simply do:
> ResultSet
> rs=stmt.next.row.in.Query.without.any.concern.for.reality(query);

Yes, of course you're correct, however my idiosyncratic polymorphism response generator is on the fritz and I can't do a thing with my hair ...

>
> of course, it is highly recommended that a specific framework
> be specially developed for for all queries of this type of SQL which
> may return more than one row. In fact, the ideal would be a specific:
> ResultSet rs=stmt.row.number.
> (var).in.Query.of.very.large.table(query);
> then the iterator simply calls the appropriate value of var while it
> is
> defined.
>

And, you're so correct, yet again. Silly me, my dipthong must be waffling in the nosegays. Harumph!

> then again, the ideal would be to cache the whole lot:
> any of this database stuff only slows down the code!
>

That's only partially true, as Tuesdays and Saturdays are exempt. Yet Wednesdays are exempt from the exemption, no?

> </tongue-in-cheek>

[tongue so far in cheek as to be out]

David Fitzjarrell Received on Thu Oct 04 2007 - 10:06:13 CDT