On 05/14/2011 05:47 PM, Greg Donald wrote:
On Sat, May 14, 2011 at 4:39 PM, Shawn Milochik<sh...@milochik.com> wrote:
I'm certain there are plenty of reasons that others could chime in with. In
any case, you're free to do it however you like. But if you choose to use
Django, be aware of the fact that a huge amount of thought has gone into the
project, and if something's there it's probably for a really good reason.
When you choose not to follow a Django convention and run into a problem
then don't be surprised.
I didn't realize trying to access my own form data directly was
unconventional, my bad.
Again, if there's anything you want to do that you can't because of the
way something in Django works, just ask.
The whole point of a Web framework is to save you (the developer) the
hassle of doing all the routine junk, such as validating/sanitizing
input, re-drawing forms with errors for user correction, writing SQL,
etc. It's always good to know how it's working and have the ability to
tweak it, as you obviously do. But as long as you have that to fall back
on it's best to let Django do the heavy (or boring) lifting for you
whenever possible.
This isn't a case of "our way rules and if you disagree then you suck."
I just wanted to make sure you don't walk away with that impression.
Shawn
--
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.
