in reply to Class::DBI vs. DBIx::Class

I have used both Class::DBI and DBIx::Class within the framework of Catalyst. As DBIx::Class has a more active and lively community, I prefer it, even when its API is not yet fully settled (it hasn't yet reached version 1 - or one could say it is version "2" of Class::DBI).

For smaller non-Catalyst programs I prefer to directly use DBI itself as setting up the OO-framework takes some time.

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

Replies are listed 'Best First'.
Re^2: Class::DBI vs. DBIx::Class
by hrr (Monk) on Jun 25, 2006 at 16:44 UTC
    Thank you for this useful insight! An active community is worth much, so I decided to use DBIx::Class for now. Setting it up and using it turned out to be only slightly more difficult (see my stumbling above) than for Class::DBI.
[reply]
      One more thing on Class::DBI (I don't know if it exists for DBIx::Class) : Class::DBI::Loader. This module waits for database access parameters and give instant access to all database table as Class::DBI objects. More, relation between all this objects (by foreign keys) are also available. A great lesson of lazyness leading to very small code (using Template-Toolkit for the view part in web development).
[reply]
        DBIx::Class::Schema::Loader is relatively new, and purports to do something similar to Class::DBI::Loader. I haven't tried it, but it judging by postings on the catalyst newsgroup, it seems to be getting popular. I'm not sure if it does foreign keys. It's not mentioned in the pod, so I guess not... but on the other hand, fk relationships aren't mentioned in the pod for Class::DBI::Loader either.

        Whatever the case, DBIX schema loader is under active development, so if there's not fk support already, maybe sometime soon.

[reply]

In Section Seekers of Perl Wisdom