On Dec 6, 2006, at 1:40 PM, John Siracusa wrote:
> 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 :)
I'm going to agree with that...
however i do somthing a little different.
i forgot the make_manager_methods and use the direct manager
method. i find that its both faster and less memory intensive.
sample:
=======
package FindMeOn::RoseDB::Object::ApiKey;
use FindMeOn::RoseDB::Object();
use base qw(FindMeOn::RoseDB::Object);
# class data here
1;
=======
package FindMeOn::RoseDB::Object::ApiKey::Manager;
use Rose::DB::Object::Manager ();
our @ISA= qw(Rose::DB::Object::Manager);
use FindMeOn::RoseDB::Object::ApiKey ();
sub object_class { 'FindMeOn::RoseDB::Object::ApiKey' }
sub load__apiKey_useraccountId
{
my ( $class, %kw_args )= @_ ;
my $results;
eval {
$results= Rose::DB::Object::Manager->get_objects(
object_class=> object_class(),
# stuff here
}
1;
=======
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/rose-db-object
