note hrr Now I understand that DBIx::Class is more flexible than Class::DBI! On the other hand, this comes at the price of longer code for simple tasks, e.g., for inserting into a table <code>'Person'</code>, one would use <code> # using DBIx::Class: $schema->resultset('Person')->new({FirstName=>'Joe'})->insert(); # using Class::DBI: DB::Person->insert({FirstName=>'Joe'}); </code> Nevertheless, the greater flexibility motivated me to try DBIx::Class, too. What still bothers me is that <code> package DB::Person; use base 'DBIx::Class'; __PACKAGE__->load_components(qw/PK::Auto Core/); __PACKAGE__->table('T_PERSON'); __PACKAGE__->add_columns(qw[PersonId FirstName]); __PACKAGE__->set_primary_key('PersonId'); package DB; use base 'DBIx::Class::Schema'; __PACKAGE__->load_classes(qw[Person]); </code> fails with <i>Can't locate object method "result_source_instance" via package "DB/Person" (perhaps you forgot to load "DB/Person"?) at c:/Perl/site/lib/DBIx/Class/Schema.pm line 75.</i> If I put the definition of <code>DB::Person</code> into <code>DB/Person.pm</code>, it works, but is far less elegant/compact. Is there a smarter solution? 557402 557422