That’s the difference.

“I never use DBIC as my model”

That’s weird, because back in January as part of this very discussion, you said:

“All my future projects will use DBIC for sure.”

But my point is that sometime a model of a single concept requires multiple tables. That’s why I use models that use DBIC, and not DBIC directly. It also made it very simple to add a Redis layer that caches the entire modelled entity, with data from multiple tables, as a single serialised blob.

I’m sure you may be able to extend DBIC to do this. In my experience you can extend DBIC to do almost everything I can think of. But I found moving my Model to Moose (and the Moo) classes, that use DBIC for storage, much simpler.

However one needs to realize that DBIx::Class::Row is (and always was intended as) A REFERENCE IMPLEMENTATION. Note how your result classes all have ‘use bas “DBIx::Class::Core’ on top – DBIC does not mandate this in any way. All it cares about is that your result class provides an inflate_result() method which ResultSet->next/all will call when it is about to return you results. *everything else* is entirely up to you. You can implement your own update/delete by calling $schema->storage->update/delete directly. You can implement your own insert(). You can *reuse* the DBIx::Class::Row logic by holding a delegate instance in your own class structure. The possibilities are endless.

The point is – you can not complain that the reference implementation does not follow your idea of an API, when the reference implementation is there *precisely* to show you how to write another set of models on top of the Schema/Storage/Resultset machinery of DBIC.

Cheers

I never use DBIC as my model. It’s always used as a tool that my models use to talk to the DB, nothing else.

I never understood DBIC plugins on Web Frameworks exactly because of this..

And yes, in the past I tried DBIC-as-my-model. You can make it work sort-of, but most of the time I spent checking to make sure none of my business methods names wouldn’t clash with the huge amount of methods DBIC adds to your objects.

Bye,

Someguy, just in case you are still reading this thread, I was wondering: does this last announcement qualify as “doing something” or…?
http://lists.scsys.co.uk/pipermail/dbix-class/2013-February/011109.html

I would take this guy’s exaggerations with a grain of salt…