Re: [Catalyst] Model/Controller logic separation - best practices?

2008-03-09 Thread Ian Sillitoe
Thanks Zbigniew. Yes, I decided to take this line after finding one of Matt Trout's replies to a related thread ("Doing work inside the DBIx::Class model"). Seems this question is being asked a lot - someone mentions an entry on the FAQ - if so, Matt's rule of thumb made a lot of sense to me: "If

Re: [Catalyst] Model/Controller logic separation - best practices?

2008-03-08 Thread Zbigniew Lukasiak
On Tue, Mar 4, 2008 at 8:35 PM, Ian Sillitoe <[EMAIL PROTECTED]> wrote: > Hopefully there is a quick and obvious answer to the following - if so, > apologies for the length of this email. Apologies in advance also if this is > considered off-topic and/or covered in previous threads - I have trawled

Re: [Catalyst] Model/Controller logic separation - best practices?

2008-03-05 Thread Ian Sillitoe
Juan, thanks for taking the time to reply. Perhaps there should be no need for the custom get_related_rows call > (and doing in the template should be, in fact, breaking MVC > principles, IMHO). If your DBIC Classes representing TableA and > TableB are properly related (master-detail, in this cas

Re: [Catalyst] Model/Controller logic separation - best practices?

2008-03-04 Thread Juan Miguel Paredes
On Wed, Mar 5, 2008 at 3:05 PM, Ian Sillitoe <[EMAIL PROTECTED]> wrote: > > Controller/TableA.pm: > $c->{stash}->{row_a} = $c->model('MyDBIC::TableA')->find('id'); > $c->{stash}->{template} = 'view_a.tt2'; > $c->forward('Catalyst::View::TT'); > > /root/src/view_a.tt2: > [% rows_b = row_a.get_relate

[Catalyst] Model/Controller logic separation - best practices?

2008-03-04 Thread Ian Sillitoe
Hopefully there is a quick and obvious answer to the following - if so, apologies for the length of this email. Apologies in advance also if this is considered off-topic and/or covered in previous threads - I have trawled around for a while (and recently got Jonathan's book !) but all my solutions