I've posted a few thoughts on this topic as well:
http://groups.google.com/group/cake-php/msg/9cd850341af29136
Also keep in mind that just because we have done something one way,
doesn't mean (unless we say so ;-) ) that that way is the best or only
way to do it. You're right in your thinking
Sonic Baker:
I guess I was kind of loose in that other posting about my definition
of business logic. Business logic to me is what RUNS the show. The
manager (controller) is what runs the show. That doesn't mean that
model (Regional Manager) doesn't enforce their own logic. Good that we
went
I agree, here here!!! :-)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL
If it helps anyone to decide on their approach, I've always thought of
data validation vs process validation. The 'Cake Way' seems to fit very
nicely with that concept.
Data validation logically sits nearest the data model - even as far as
triggers and/or stored procedures within the database if
On 9/27/06, Chris Hartjes [EMAIL PROTECTED] wrote:
Placing data validation and other data
munging in the model seems to be the way of this definition. Food for
thought, that's for sure.
I second that. Data validation rules (or business logic/business
rules) should be enforced on your data at
Thank you God, Budda, The Universe, and every other representation of
the higher power for influencing Chris into making this post.
As explained in the previous post,
I'm in the process of re-writing my application to put all data related
functionality in the Models (where it used to be in the
On 9/27/06, Sonic Baker [EMAIL PROTECTED] wrote:
Thank you God, Budda, The Universe, and every other representation of the
higher power for influencing Chris into making this post.
It was a bit of serendipity really that led me to doing it, and I'm
glad I could help you out. However, I feel
On 9/27/06, Chris Hartjes [EMAIL PROTECTED] wrote:
However, I feel it important to point outthat adherance to standards for adherance's sake is a common anddangerous practice for developers.
Well it was more of a worry about being totally wrong than adhering to
standards with a little 'code with
