On 5/11/06, Ned Batchelder <[EMAIL PROTECTED]> wrote: > Django provides a great way to separate models and views, and even > pre-populates the project tree with directories named models and views. > But what about separating models and controllers, that is, separating > the specific database representation of an object from all of the > "business logic" needed to manipulate the object? > > I've seen two patterns in use, and neither is completely satisfactory. > I'm wondering if there are possibilities I've overlooked. > > The first technique is to put all of the logic in the model class. This > leads to large model classes, and combines all of the field lists with > the logic to manipulate them.
If I'm understanding you correctly, I would argue the logic goes in the model class. Models are intended to contain all data and logic about that type of object; this way, everything model-related lives in one place. As you point out, this means sometimes models have a lot of methods, but I don't see how that's a problem in practice. Does this answer your question? Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
