> > Well in my code, the iterator i wrote kept a reference to the
> > underlying result set.
>
> the problem is not having a reference to the result set, but having a
> reference to the query object. the structure, afaics is that the OQLQuery
> object has a reference to its result set, but not vice versa. when
> OQLQuery goes out of scope, it is garbage collected, and in its finalize
> method calls resultSet.close() - so you still have a reference to the
> result set, but its closed....
>
> I'm happy to be corrected, but thats my reading of it.
That sounds quite true.. and would explain the problems i was having with
it. I'd be very interested in your patch, ill give it a run see if it
fixes my problems also....
--
[EMAIL PROTECTED] Do not meddle in the affairs of dragons, because you are
crunchy and taste good with ketchup.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
