On 5/25/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
i need to pull this info quite a bit. would it be bad form to add it into the a Manager derived class as such?==== package MyApp::RoseDB::Object::UseraccountAsset::Manager; use Rose::DB::Object::Manager; our @ISA = qw(Rose::DB::Object::Manager); sub object_class { 'MyApp::RoseDB::Object:: UseraccountAsset ' } __PACKAGE__->make_manager_methods('useraccount_asset'); sub get_useraccount_asset__full { my ( $class, $id , $db ) = @_ ; return $class->get_useraccount_asset( query=> [ useraccount_id => $id, ], require_objects => [ 'asset' , 'asset.asset_type' ], db=> $db ); }; ==== [...] i'm thinking that this is the way to do it.
Yep, that's exactly what the Manager class is for. Add all your custom multi-object-manager-type methods to the Manager class. The "default" ones are just a staring point. -John ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642 _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
