Thank you Waylan for your comments. I've found the developer discussion about this (searching the group for "auto_now_add" does not find the result! wow! Google missing an easy hit?). http://groups.google.com/group/django-developers/browse_thread/thread/4cd631c225cb4e52 . This solves the problem sufficiently. Thanks.
On Sep 10, 12:21 pm, drozzy <dro...@gmail.com> wrote: > Well, that is the purpose of that. I mean if you want a custom field > that saves only on Thursday, it makes sense to write a modified save > routine.. > > On Sep 10, 1:19 pm, Andrew Gwozdziewycz <apg...@gmail.com> wrote: > > > > > On Thu, Sep 10, 2009 at 9:35 AM, Ryan K<ryankas...@gmail.com> wrote: > > > I'm trying to give advice to people but I can't even figure it out > > > myself (even though it works for me just fine -- so far?). > > > Last week, I ran into a problem using them because I wanted to set manually > > the date in certain situations. auto_now sets it to datetime.datetime.now() > > *everytime* it's saved, which means you can't actually set it manually. > > Thus, > > you have to be careful, and overriding save() may be a better option in some > > cases. > > > --http://www.apgwoz.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
