http://qs1969.pair.com?node_id=505085


in reply to Re^2: A brief survey of the DBI usability layer modules on the CPAN
in thread A brief survey of the DBI usability layer modules on the CPAN

I really wanted to like Class::DBI; but if you actually use your database relationally, it gets in the way too much.

Yes, this is actually the biggest of the wrinkles I was talking about in my node. Complex operations end up being processed in the client instead of within the database, as it should be.

(...) anything that involves multiple joins, f.ex., is at best difficult to express. I instead frequently found myself grepping and mapping through lists of result objects; which is just a waste.

Precisely. And although I haven't looked into this yet, I am quite sure it is possible to express these relations and let the object hierarchy sort the proper SQL statements to generate so as to minimize the amount of data fetched.

I have the impression that Class::DBI is a step in the right direction, but more control is needed. I think that improving the statement generation would be a big step.

Best regards

-lem, but some call me fokat

Replies are listed 'Best First'.
Re^4: A brief survey of the DBI usability layer modules on the CPAN
by Aristotle (Chancellor) on Nov 02, 2005 at 20:38 UTC

    I think that is better done with an approach such as SQL::Abstract’s. (Indeed, I’d be using it even now, if I hadn’t run into the previously mentioned limitations.) An object-relational mapper, as far as I can tell, will always suffer from trying to express queries with complex dependencies using an ill-suited model.

    Makeshifts last the longest.