I was wondering if this design point/flaw is still valid:
QueryLoader gives ResultSet and PreparedStatement to iterator.
Every time Qeury.iterator() is called, it executes queries. So, if you do not iterate code to the end it leaves PS, RS open. close()-method is only called if hasNext() is false. (postNext())
Commit does not close these since it does not have access to them .
This code leaves preparedstatement open and finally after 100-200 open preparedstatements hibernate crashes:
I think this is a major design issue. Is this considered as bug or "it works like this, just iterate to the end and use proper SQL-queries"?
Whole iterator-logic needs redesign
Hibernate 3.1.2, Oracle 188.8.131.52
In an effort to clean up, in bulk, tickets that are most likely out of date, we're transitioning all ORM 3 tickets to an "Awaiting Test Case" state. Please see http://in.relation.to/Bloggers/HibernateORMJIRAPoliciesAndCleanUpTactics for more information.
If this is still a legitimate bug in ORM 4, please provide either a test case that reproduces it or enough detail (entities, mappings, snippets, etc.) to show that it still fails on 4. If nothing is received within 3 months or so, we'll be automatically closing them.
Bulk rejecting stale issues. If this is still a legitimate issue on ORM 4, feel free to comment and attach a test case. I'll address responses case-by-case. Thanks!