Re: How strict is your approach towards convention over configuration?

You so I get this right:

1. I would need models for the "real" tables,
2. I would then need views for those,
3. Then I'd need other models for those views

4. And that's where we'd really start?

I'm asking this because the old codebase (we'll _not_ use) is already
complicated and bloated, the database is basically a pile of crap and
designing a "strange" workaround would probably do _my_ job but would
not improve anything for the future where somebody (most certainly
without a clue about all these models -- who reads docs...) will mess
it all up again.

I was hoping so much for a slick and transparent way to do this.

However this turn out I appreciate your effort answering, thank you :-D
Enno

Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.

You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en