> Why not create it there? That is the moment you have all the data you > need and all you're doing is calling a constructor. The code you've > written there is a pretty normal pattern for taking form information and > putting it into a model.
Because it forces me to make different view for each model. Its very difficult for novice to understand which logic should be placed in views, which on models. Is there a resource with django-patterns or good programming practices ? > By the way, you might want to investigate form_for_model() (see the > newforms documentation again) if you are taking all your form data and > putting it into one model. Its pretty useful thing but I not for relation like Model -> Usermodel, which user object should be taken from request.user not from POST like in exampe above. > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
