On Aug 7, 6:55 pm, David Danier <[EMAIL PROTECTED]> wrote: > > However, I'm a little confused now. I > > thought the problem was only validation, and not the actual data that > > was added to the choice list. > > The problem is, that validation does not use the actual data of the > choice list. > > I think doing so may even become a security issue, as people may guess > valid IDs that they should not use (for example if you use > user_profile.some_relation as the queryset).
Well that was the point I was trying to make, but I probably didn't word myself as clearly as I should have :-) Validation is done using a (possibly) different set of data than the choices displayed to the user. > Perhaps it could be changed to only allow choices in the queryset, but > an option is added to ModelChoiceField to use the default manager? 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. Cheers, Nick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
