in reply to Why use an OO -> SQL mapper module?

You also asked for examples of how it can make things easier. Here are some code nodes with DBIC.

One of the punchlines kind of buried in there is this shopping cart method– 

sub checkout_total {
   +shift->items->get_column("cost")->sum;
}

[download]

DBIC starts to get extremely powerful in a short space and if treated correctly can be highly semantic and self-documenting. Chained ResultSets are another part of this but aren’t covered in my examples. They are in the Master Class XUL, linked in one of those, which is definitely worth a look.

Replies are listed 'Best First'.
Re^2: Why use an OO -> SQL mapper module?
by chromatic (Archbishop) on Aug 13, 2011 at 01:05 UTC

    Chained result sets are immensely useful. Certainly I could write the necessary SQL by hand, but chaining result sets mean that I don't have to!

[reply]

In Section Seekers of Perl Wisdom