Yes, I've created a custom clean method to deal with this for now, thanks.
Perhaps the docs should be updated to have a note on that example. On my page, I wanted to include an initial "http://"; value so users would not be confused as to what was expected in the field, but the field was also optional. On Aug 26, 3:23 am, "Peter Melvyn" <[EMAIL PROTECTED]> wrote: > On 8/26/07, Shev <[EMAIL PROTECTED]> wrote: > > > 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. > > Even if you supply a valid inital value? It does not sound well for me... > > If you need such behaveour, should not you sublass a field and > override the clean() method? > > Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
