Once I used this kind of way and it really works. It's only kind of tricky to decide, when to call validators for each of the manipulators and when to save, if there is a relationship between the two models, for example: 1. if A and B are not saved, how to validate B, that has to be related to A, when A still has no primary key to assign to B. 2. should at first A be validated and saved, and only then B validated? If B is not valid, should A be deleted?
As I've never used custom manipulators for this reason, it would be interesting to know is it easier to use the custom manipulator or this approach. Good luck! Aidas Bendoraitis [aka Archatas] On 9/22/06, Michael Radziej <[EMAIL PROTECTED]> wrote: > > limodou schrieb: > > No, I think you cann't do this in django. You should use custom > > manipulator for this. > > Hmm, I think you could use it like this: > > ... > form1 = forms.FormWrapper(manipulator1, data1, errors1) > form2 = forms.FormWrapper(manipulator2, data2, errors2) > return render_to_response(template, > context_instance=RequestContext(request, "form1": form1, > "form2": form2, ...)) > > > I'm not sure if this works out, and how you'd separate > request.POST into the two data dicts, and whether this is > necessary at all. Perhaps it's a way. > > Though, I don't know if this is better than the other approach > with the custom manipulator. It's an interesting question. > > Michael > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
