Noons 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!
> 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);
>
> 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.
Sadly that 'design pattern' isn't due to be published until 2010 with
the announcement of web 3.0 - not by a publisher but by a global
telecoms network. The paperless office will follow shortly thereafter
only delayed by the cosmic entropy that requires a pre-existing
paperless toilet.
--
Niall Litchfield
Oracle DBA
http://www.orawin.info/services
Received on Thu Oct 04 2007 - 13:28:11 CDT
