Thanks so much for your help Ryan. Unfortunately though, I think I'm missing some crucial bits of detail here so I still have a couple basic questions:
(1) Where should my custom manipulator code live? I would think it's in the view, since it really is view code after all. But maybe the need to associate it with a model means it has to live in the model? (2) Ryan said "If your custom manipulator is for creating a new instance of the model, just have save() create on and return it." -- how do I make my custom manipulator create a new instance of the model? This is really the crux of my initial question I think -- and the docs really don't seem to address this at all. Please help! -- my deadline is looming! :-) Thanks all, Sean On Sep 4, 2006, at 11:19 PM, [EMAIL PROTECTED] wrote: > > If your custom manipulator is for creating a new instance of the > model, > just have save() create on and return it. > > When I am writing a custom change manipulator, I either pass the > instance being changed to the __init__ method and save it as > self.model_name or pass it to the save() method and use it instead of > creating a new one, depending on the situation. > > I don't know if that's the standard solution, but it seems to work. > > > > > > :::: DataFly.Net :::: Complete Web Services http://www.datafly.net --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
