On 12/6/06, Michael Reece <[EMAIL PROTECTED]> wrote: > it seems like an intriguing idea, but what headaches might one run > into with this approach?
All of those things are perfectly possible. The downside to all of them is namespace pollution. The recommended approach, with separate ::Manager classes, gives each manager its own namespace in which to add custom methods. Putting manager methods into the row class may cause conflicts with column or relationship accessor methods (or any other other row-related methods). Combining all managers into one master class would result in even more possibility for name conflicts. I'm quite a stickler for namespacing. YMMV :) -John ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
