in reply to DBIx::Class with two kinds of otherwise identical table types

While I have indeed doubts that setting up multiple totally similar tables for totally similar data is the right way forward, I do not think you can spare yourself the trouble of writing only one class for all of these. DBIx::Class works on the assumption of "one table = one package" and unless you really want to experiment yourself with inheritance and such (and who knows what that may break somewhere in this ORM), I think you will need a separate package for each table.

Of course DBIx::Class::Schema::Loader can largely automate that whole process.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

  • Comment on Re: DBIx::Class with two kinds of otherwise identical table types

In Section Seekers of Perl Wisdom