[ http://issues.apache.org/jira/browse/IBATIS-226?page=comments#action_12358088 ]
Jeff Butler commented on IBATIS-226: ------------------------------------ Paul, it seems that you have caching requirements that are really beyond the capabilities (current or imagined) of iBATIS. It's best to think of iBATIS as caching result sets - not "objects" in the sense that you need them. This is a fundamental difference between what iBATIS does, and what you seem to need it to do. I would seriously suggest that you investigate some other object caching solution that is more appropriate for your particular problem space. I doubt that iBATIS will ever get where you want it to be, it's simply not designed for that purpose. You could still use iBATIS for data access, but check your own cache first before calling iBATIS. Alternatively, dare I say it, would Hibernate be a better fit for your system? They've spent a lot of time (and lots of code) trying to understand object identity and caching. As far as I know, we don't ever plan to deal with object identity in iBATIS. BTW - I would make this same comment for IBATIS-222. > Support Commons DBUtils ResultSetHandler > ---------------------------------------- > > Key: IBATIS-226 > URL: http://issues.apache.org/jira/browse/IBATIS-226 > Project: iBatis for Java > Type: New Feature > Components: SQL Maps > Reporter: Paul Benedict > > Sometimes I need total control over the caching mechanism for very critical > systems. I need to also guarantee object identity and I can only do this when > handling the result set myself. I propose adding an attribute to the > <statement> tag (and also <select>, <insert>, <update>) that will specify a > subclass of ResultSetHandler so that I may write custom code and decode the > ResultSet myself. The ResultSetHandler class is part of the Jakarta Commons > DBUtils package. It is extremely useful! > <select id="findMyObject" resultSetHandler="com.company.MyResultSetHandler"> > To prevent excess object creation, IBATIS must reuse the same instance it > creates. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
