On Wed, Jul 29, 2009 at 10:23 PM, Jonas Obrist<ojiido...@gmail.com> wrote: > > I tried to add support for an opposite of 'choices' to DB Fields (namely > CharField) but failed horribly. I still think that would be a nice > feature so I thought I'd bring this to this group. Maybe someone can > implement this. What I had in mind was an option reserved_names (or > however you want to call it) which is the opposite of 'choices', meaning > you can enter anything as long as it's not in reserver_names.
This sounds like it might be a better match for the model validation code that has under development for some time. Excluding a particular set of names is just one example of a validation condition that might be violated. We will be better served by solving the general problem instead of a specific problem, and we've already committed to solving the general problem. Honza Kral's Summer of Code project is where you should be looking. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
