id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux 4893 remove superfluous field options David S. Adrian Holovaty "Field options formerly specific to the admin interface (e.g. {{{blank}}}, {{{choices}}}) remain in the newforms-admin branch. The rationale is that they are or could be more generically useful for data validation. This confuses real database constraints like {{{null}}} with these programmatic 'constraints'. Their applicability is ambiguous. Looking at the 2 examples, both would be better left to whatever app is working with the data. There is nothing inherent in being able to be {{{blank}}} for example, even in the admin. That is, with the new admin.site functionality, it is perfectly reasonable to imagine that you create 2 admin views for the same model, one of which needs a field to be 'blankable' because it fills the value, while a second view permits the value to be manually entered. Likewise, 2 admin views might want different choices for a particular field. Specifying {{{choices}}} in the model is either too restrictive or just confusing. Of course, it might be that what you really need is choices modeled in the DB as foreign key lookups, but that further obviates the need for {{{choices}}} at the model level. Removing these kinds of options will simplify and better focus the model interface. related links: * http://groups.google.com/group/django-users/browse_thread/thread/ccec4062d37bcae7/7fc869b45ac8c983#7fc869b45ac8c983 " closed Database layer (models, ORM) dev wontfix newforms-admin admin fields options validation Unreviewed 0 0 0 0 0 0