> Sounds like a bad idea to me. unique_together doesn't exist on a specific > field precisely because it isn't an option for any specific fields, it's for > a set of fields. All the other options belond to specific fields. > > Alex
You're probably right about this, but (while we are on the subject) aren't there some things that shouldn't be part of the model field options that currently are? Why is help_text part of the field definition? This is a ui-specific thing--what does it have to do with the database? All abstractions are leaky, sure, but this seems inappropriate. The same thing goes for editable, error_messages: these options are not part of the ORM, they are parts of the forms subsystem that have somehow ended up in the ORM. Why should the ORM know anything about forms, or any other part of Django for that matter? Eduardo -- 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.
