noted . Thank you Malcolm . On Sun, Jan 11, 2009 at 3:17 PM, Malcolm Tredinnick <[email protected]> wrote: > > On Sat, 2009-01-10 at 21:38 -0800, Dmitri13 wrote: >> Hi Guys, >> I am unable to save to table TEST_QST ,it returns error QstForm >> object has no attribute 'save' >> I have confirmed that >> form.is_bound returns true >> form.is_valid returns true >> I have included my code in this post > [...] >> # Create the form class. >> class QstForm(forms.Form): >> qst_id = forms.CharField(max_length=8,widget=forms.HiddenInput) >> test_id = forms.CharField(widget=forms.HiddenInput) >> test_cat_id =forms.CharField(widget=forms.HiddenInput) >> qst = forms.CharField >> (max_length='200',widget=forms.Textarea ,label='') >> status = forms.CharField(widget=forms.HiddenInput) >> active = forms.BooleanField(widget=forms.HiddenInput) > > There's nothing too mysterious going on here. QstForm is a subclass of > forms.Form. The Form class doesn't have a save() method, since saving > doesn't make sense. What would it save to? ModelForms have a save > method, since they're proxying for the underlying model and you can save > a model. > > For a normal Form, after validating, it's up to you to decide what to do > with the data in cleaned_data. You could put that into one or model > objects and save them. Or do something entirely different with it. > > 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 -~----------~----~----~----~------~----~------~--~---
