I get what you are saying, you are right in that it might make more sense to do it for every field that needs it. Thanks.
On Sep 20, 11:22 am, Shawn Milochik <sh...@milochik.com> wrote: > There are always ways. You could subclass models.Model and add the behavior, > if you read enough to understand how Django's models work. > > However, since you're only going create a model once (except migrations > later), is it really going to save that much work? > > If you want to do it a quick & dirty way, you could write a Perl one-liner > (or a Python script) to read your models.py and automatically output the file > with additional lines after each models.*Field line. > > Shawn -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
