On Feb 4, 2:21 am, ds39 <sdavid...@gmail.com> wrote: > Thanks to everyone who took the time to respond. I've been looking at > the godjango website, and its been very helpful with figuring out > forms. I was able to modify some of the tutorial examples on the site, > adding form.save(), to successfully enter text into the database. So, > I think I've found my answer. The only other thing I was curious about > was when and when not to use something like ModelForms with user- > entered data. For instance, are there times when text responses > associated with different users should be handled some other way ?
When it suits your needs. Sorry for the stupid answer :) You have basically three ways to do form processing. ModelForms is the easiest, everything is easy and magical. The only problem is that there is happening a lot behind the scenes, and it can be hard to get full control of things when using ModelForms. Next choice is regular Forms. There isn't much magic, they take some data in, validate it and convert the data into Python values. However, even this can sometimes limit your options. So, the last way is to not use Django's forms at all. Just use request.GET and request.POST directly. This can come handy if you really need it. But you almost never need to go this route. So, if you find out that ModelForms are hindering your development instead of accelerating it, try without ModelForms. Otherwise, there really isn't any rules when to use what kind of form processing. - Anssi -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
