To fix my typo above: > I could also override my model's save() method, but I don't think I > would be able do anything about invalid data other than refuse to > write them to the database. I don't think there's an exception
...that I could throw that would inform the view that called save() what went wrong. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
