2009/5/17 sampablokuper <sampabloku...@googlemail.com> > I've been encountering the same problem. It's especially frustrating > because it seems model validation used to be much easier in Django > (see > http://www.cotellese.net/2007/12/11/adding-model-field-validation-to-the-django-admin-page/ > ). > [...] > > Are the Django devs working to re-create model validation in a way > that would bring this missing functionality back to Django, or do they > think that people really ought to be breaking DRY by having to put > this stuff in every form that references a model for which you have > custom (though not uncommon) validation requirements? Or is there some > other way to do this that is better than both the aforementioned > options?
I've just found some discussion of the issue over here: http://groups.google.com/group/django-users/browse_thread/thread/6b2c1df18b73bf55/3ef0cdc1d3039fbc?lnk=raot I'm pretty astonished that this feature has been pushed back to v1.1 - to my mind, model validation is an absolutely core ability for a web framework to possess. My faith in Django has just been shaken, *hard*. :( --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
