On Tue, Apr 20, 2010 at 11:40 AM, Eden Cardim <[email protected]> wrote:
> > This is the point where you should start considering an intermediate > layer between DBIC and your application. When designing new > applications it's recommendable that you stay away from methods that > imply knowledge of your store architecture (such as create, update, > search and insert). > Can you point (or show) and example? Yes, another layer would be good, although I'm kind of using Catalyst for that now -- all access to the model is via the Catalyst-exposed API. So, POST /Cd is that abstraction. I can add the mapping into Catalyst (which is what I'm already doing) but it would have been cleaner at the DBIC level. Maybe a layer between is in order. Thanks, -- Bill Moseley [email protected]
_______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
