hi martin,
I have just run several tests with different hints. It works very well, however, if I don't set a hint, no cursors are used, even with getIteratorByQuery!
But maybe that's not too bad. If you enable cursors on iterators by default, MySql users could run into troubles.
I just found this on the mysql side:
/There are some caveats with this /(using a cursor)/ approach. You will have to read all of the rows in the result set (or close it) before you can issue any other queries on the connection, or an exception will be thrown. Also, any tables referenced by the query that created the streaming result will be locked until all of the results have been read or the connection closed.
*http://dev.mysql.com/doc/connector/j/en/cj-implementation-notes.html*
/
just a question: can I apply your patch easily to the 1.0.3 sources? I don't know how stable the current OJB_1_0_RELEASE branch is.
regards, andreas
Martin Kal�n wrote:
Have a look at http://issues.apache.org/jira/browse/OJB-31
This is now fixed (in beta state) in the OJB_1_0_RELEASE branch, where you can set a global max cap hint through the connection-pool descriptor in your repository.
All Iterator objects should also set fetchSize hints of 1 internally in OJB -- so please give it a try without setting any hint at first, and see if you get better results automagically.
Regards, Martin
P.S. This will also be merged with the trunk (v1.1 pre) eventually. I will re-open the issue in JIRA and set the status there once it has been done so you can add yourself as observer of OJB-31 in JIRA to get mail notification on updates.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
