Hi All,
We're in the process of porting an existing CMS/Cart system to Catalyst,
and trying to work out how to deal with the database modelling. While
most of the tables will be accessed through a simple DBIx::Class::Schema
setup, there are a few which have more complex relationships that we
wish to hide behind custom methods.
We've come to the conclusion that this is best done by creating an
external module, but we're not sure whether we should create two
Catalyst models (one using DBIx::Class::Schema and one wrapping our
external module), or have a single model and access the simple tables
through the external module too. The first option seems simpler more
straightforward, but we don't want to end up with multiple database
connections (there is only one database) if we can help it.
Can anyone offer some advice?
Thanks,
--
Jamie Neil | <[EMAIL PROTECTED]> | 0870 7777 454
Versado I.T. Services Ltd. | http://versado.net/ | 0845 450 1254
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
