> That could work. The main point of this thread was to see if there are > use cases for using the default manager for validation instead of the > query set because I couldn't really think of any - but I'm sure there > could well be some.
Like the one I explained? :) I think the strongest argument against using adding an extra "validation queryset" argument is that it doesn't give the flexibility of programmatically validating data. A function works much better in this respect. And as for the default behaviour, I've put forth my thoughts on it and I think it is more commonly a problem than the security issue that was suggested (since you probably won't usually construct your forms to allow a user to have any say in their own access). Not incidentally, this is what the "validator_list" has been used for. However I'm not sure if this will remain in place since oldforms is going away... but you should be able to transition it easily if necessary. -rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
