> How about writing your own constructor that takes an argument of type > and has a default value assigned there?
I guess I don't understand where this constructor lives in the food chain. It can't exist prior to the first save() of the object because we don't have the id before that. I tried putting it *in* the save() and it did nothing. (BTW, that last one really bothers me.) Or are you talking about a constructor for the edit form? That might work, if I can figure out how to inject it at the right place. I think I need to stare at the db/forms code for a while. Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
