> I was wondering what everyone's stance is on inclusion of something like this.
It is not really needed, you can override the field. Take a look at the __init__ call in http://www.djangosnippets.org/snippets/26/ and you can do that with a model field as well as a form field. Yes it is a bit of a pain but you won't need to do it very often, especially since you can use the field again and again (i.e. in different models). Apart from not needing it, a fairly weak reason against including it is that if your query gets large, it becomes unusable (i.e. choices gets too long). Also you might not want to use __unicode__ or __str__ in the choices field but something shorter or more specific to the model that is referencing it. To me it seems more sensible to create a single custom field which you can change in just one place. BTW, it probably would be better to post first in DJ Users. People have worked through problems like this already and have some pretty neat solutions or ideas to some interesting problems. -rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
