On Tue, 02 Aug 2011 12:11:45 -0400, Terrence Brannon <scheme...@gmail.com>
wrote:
On Sat, Apr 17, 2010 at 12:48 PM, Paul Bennett
<paul.w.benn...@gmail.com>wrote:
http://code.google.com/p/perl-**dbix-nailgun/source/browse/<http://code.google.com/p/perl-dbix-nailgun/source/browse/>
somehwat reminiscent of the recently updated DBIx::DataModel by Laurent
Dami. It looks like you manually describe table relationships instead of
having a "Loader" class figure all this out.
At any rate, a full set of code samples for all common CRUD operations
against the Sakila database is a welcome submission to DBIx::Cookbook.
The example for fetching all records are shown for Rose::DB::Object,
DBIx::Skinny and DBIx::Class -
http://search.cpan.org/~tbone/DBIx-Cookbook-0.07/lib/DBIx/Cookbook/Recipe/Searching/fetch_all.pod
I did many more operations for DBIx::Class.
Does this belong in CPAN (once it's finished off and polished a decent
bit more)?
why not?
For whatever it's worth, after discovering DBIx::Class independently a few
weeks ago (when we were looking at moving to Catalyst for the next version
of the app I get paid to hack on (as opposed to the sometimes-bizarre
shenanigans I choose to hack on for free)[*]. Looking over the docs and
source of DBIx::Class, I have officially consigned DBIx::Nailgun to the
bit-bucket. Everything it tries to do, DBIx::Class does better, and
besides the latter has been worked on by minds far more noteworthy (and
apparently capable) than mine. I'll probably be taking down the Google
Project for it, though leaving it up for posterity seems like it might
have sentimental value (and maybe real value for some other coder).
[*]Moving to Catalyst / Moose / DBIx::Class seems to be much harder than
developing for them from the ground up, and we're *so* not in a position
at work to re-develop from the ground up right now.
and what does "DTO" stand for?
"Data Transfer Object", more or less something like "thing that wraps
database operations up in a nice, clean ${language}-friendly interface".
This differs from ORM in subtle ways that I'm not equipped to describe.
ORM seems to have both a broader and narrower scope, or something.
--
Paul Bennett (PWBENNETT)
