When model method gets 'request' parameter its 99.99% ill-formed design of application. All request/response handling and most of business logic have to be in views.py or similar but not in models.py.
On 7 янв, 12:38, Darthmahon <[EMAIL PROTECTED]> wrote: > Hey, > > I've just started working on my project but before getting too far > down the line I wanted to ask the opinion of people on here. > > I've seen some code examples that show functions within the models.py > file like so: > > ######################## > from django.db import models > > class SaveArticle(models.Model): > .... > def SaveNew(request) > .... > > ######################## > > Is there any particular benefit of nesting these "functions" within a > class? Or is it ok to simply put them into the views.py file? > > Just wondered what best coding practice was. > > Cheers, > Chris --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
