[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-758?page=all ] Max Rydahl Andersen reopened HBX-758: ------------------------------------- found a couple of issues i need to fix before closing it. first thing is that index info puts a string instead of a boolan into the map. the other is that i get "maximum cursor exceeded" when i fix the above error ;( -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-758?page=co... ] Max Rydahl Andersen commented on HBX-758: ----------------------------------------- no problem I fixed them both now (sorry for not updating) the classcastexception were being swallowed with a too friendly catch clause which i now changed + fix the actual value. The cursor issue is "fun" because it is exactly the same thing that happens with the jdbc metadata api on Oracle (and only oracle) and the fix (on your metadata dialect) is to pass in the Statement used when iterating a resultset so it will be closed together with the resulset. Then no cursor leaking is to be found. The fun part is that in the pure metadata api there is only the resultset to close so it looks like Oracle does not close their metadata Statements.... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-758?page=co... ] Max Rydahl Andersen commented on HBX-758: ----------------------------------------- ResultSetIterator now take an optional statement that can be closed when the result set gets closed. regarding performance then i haven't looked into that part yet, but it shold definitly be faster for foreignkey lookups (and as long as you don't reverse engineer the complete schema) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira