No, invalid data should not pass. But neither should an initial field value raise an error when the POSTed data is exactly the same as the starting value; it should just be ignored and the value discarded.
On Aug 25, 7:32 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > On 8/25/07, Shev <[EMAIL PROTECTED]> wrote: > ... > > > However, what I'm seeing is that when I actually do set > > initial='http://' for a URLField, either in the field definition above > > or via passing in a dictionary for dynamic initial values, if I then > > submit/POST the form without changing the URLField, it gives an error > > that the URL is invalid (of course 'http://' by itself is not a valid > > URL). Shouldn't the validation step know to ignore a form field value > > if it's the same as the initial= value?? > > You'd prefer invalid data would pass validation? > > If you provide an invalid initial value, I'd expect it not to pass. No? --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
