On Thu, 8 Feb 2007 23:16:24 -0500 Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
JV> I've been doing a lot of repetitive operations on the results from JV> manager functions lately. JV> Today I think I realized a functionality that might make sense -- if JV> the results returned by a manager call weren't simply an array, but a JV> class object. JV> It would behave just as an array - there would be no real difference JV> in current functionality. perhaps a tied array or blessed reference. JV> By default, there would be a Rose::DB::Object::ManagerResult class JV> that does basically nothing but support common array functions. JV> Calls to manager functions would then accept a manager_result_class JV> parameter , which is the name of the class to return the result as JV> ( defaults to Rose::DB::Object::ManagerResult ) JV> given a list of manager results, one can then further filter the JV> results without hitting the db, or easily loop through the items to JV> do a repetitive task It may be useful if you want to filter the results in several *different* ways, but I'd rather do it in SQL with the search functionality of RDBO. I'd worry about people that, rather than doing a search correctly, stack filters on top of a global SELECT. I think foreach/sort/grep do most of what you describe already, and they don't need a special class to do it. Introducing yet another class into the hierarchy would complicate things. Ted ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
