I would like it to appear as if it was a default value for the object, to be honest. :) And by that I mean I would like to be able to display the default-value of date_created on the create page (and the actual date_created of the object on an edit page.)
Doing it in save() doesn't help. Doing it before manip validation doesn't help. I need to have multiple codepaths setting this default value, which is what I was trying to avoid. (Yes, I can create an abstracted function, but it's complexifying my already-complex view code) In a nutshell: Why should the behavior of default values differ based on whether they are in an editable html form? That just seems fundamentally wrong to me. :) In the meantime, I guess I'll need to do the multiple-code-paths route. (And figure out how to balance-out strings versus dates so they get set in the correct format in the correct places.) Thanks, Mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users -~----------~----~----~----~------~----~------~--~---
