I would argue that having *any* dbix create/update/delete/find etc.
methods in a controller is bad practice.
I agree.
in controller i also do translation of web parameters names to business
parameters names.
but what about user authorization check, which depends
on business data and business logic.
it should be done in controller?
(otherwise session data should be send to model as well)
--
regards
piotr
_______________________________________________
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]
