On 5/3/06 5:58 PM, Guillermo Roditi wrote: > Normally I would just create an aggregator class that managed the dispatching > of the right object types and queried all tables and merged the results
That sounds like a fine solution to me. > but I'd like to make something that can more closely iterface with Rose and > the Manager. Kind of like a 'fake' object that I can use in the > meta->relationships and that will hopefully even play nice with > load(with=>'props'). Do you have any idea as to what would be the cleanest > way to implement this? I'm not sure what you mean, exactly. Can you provide some example code showing your proposed class in use? > or am I missing something much more obvious? In most cases where you feel like you want to combine or aggregate objects of multiple existing RDBO classes, there are two solutions. The first is to do just that: aggregate and delegate. It's straight forward and easy to understand. The second is to create a database view that combines the data from the relevant tables in the way that you want, then make an RDBO class on top of that view. That'd be read-only, unless your database supports updatable views. -John ------------------------------------------------------- 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
