-Message d'origine-
De : Matt S Trout [mailto:[EMAIL PROTECTED]
Envoyé : jeudi, 27. septembre 2007 22:44
Don't confuse class -names- with the nature of classes.
MyApp::Model:: is
*adapters* that make a model available to MyApp, not where
your domain model
logic itself should live.
On 9/27/07, Matt S Trout [EMAIL PROTECTED] wrote:
I usually these days have MyApp::Web for the catalyst app instead of MyApp so
I can deploy things like MyApp::DataStore from a separate dir tree.
How do you deal with configuring the database connection for things
like cron jobs outside of
Hi,
On Sep 28, 2007, at 8:55 AM, Ian Docherty wrote:
MyCompany::MyApp::Controller
MyCompany::MyApp::View
MyCompany::MyApp::Model
MyCompany::MyApp::Schema (where my ORM goes)
MyCompany::MyApp::Logic (where my other business logic goes)
I originally created the 'Logic' namespace because I was
Hi,
On Sep 27, 2007, at 11:51 AM, Ian Docherty wrote:
In a previous thread, Matt S Trout said.
The model -is- where your business logic lives.
The real question is whether your ORM should be directly in the
model or
not, but that's a whole different thread.
Based on this I have the
Pedro Melo wrote:
That's what I do with two minor adjustements:
* I started using load_namespaces to control each source resultset
class also;
* I don't put my model inside the catalyst application.
And is load_namespaces significantly slower than using load_classes with
all classes
Ian Docherty wrote:
I don't see how this helps me with the namespace in Catalyst, if I use
$c-model('DBIC::Demo') won't it still come back with the namespace
MyApp::Model::DBIC::Demo?
my bad: Stupid of me to think it matters. That's what inheritance is all
about!
On Thu, Sep 27, 2007 at 11:51:26AM +0100, Ian Docherty wrote:
In a previous thread, Matt S Trout said.
The model -is- where your business logic lives.
The real question is whether your ORM should be directly in the model or
not, but that's a whole different thread.
Based on this I have
