Re: auto_now_add and auto_now
On 13 oct, 17:15, Brian Beck <[EMAIL PROTECTED]> wrote: > On Oct 13, 8:38 am, "Mike Scott" <[EMAIL PROTECTED]> wrote: > > > Secondly this question has been asked, and solved many times. If you search > > through the django-users archives I'm sure you'll find plenty of solutions. > > There are solutions out and about in the blogosphere too. > > Actually I think this is an appropriate place to ask since the > resolution (which was unclear) never resulted in action. I was > confused about these myself just yesterday because the documentation > doesn't mention anything about possible future deprecation. The only > action was three months ago with a DeprecationWarning patch that isn't > checked in. Thanks Brian, that why I ask here, I was really confused. Thierry. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: auto_now_add and auto_now
On Mon, 2008-10-13 at 08:18 -0700, Brian Beck wrote: > On Oct 13, 11:15 am, Brian Beck <[EMAIL PROTECTED]> wrote: > > The only action was three months ago with a DeprecationWarning patch that > > isn't checked in. > > ...and probably shouldn't be, since it still doesn't update the docs. The fact is that these attributes are in 1.0 and documented. So they're part of the stable API, for better or worse (I would have preferred to see them removed, but I'm as guilty as everybody else of forgetting about it). Regards, Malcolm --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: auto_now_add and auto_now
On Oct 13, 11:15 am, Brian Beck <[EMAIL PROTECTED]> wrote: > The only action was three months ago with a DeprecationWarning patch that > isn't checked in. ...and probably shouldn't be, since it still doesn't update the docs. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: auto_now_add and auto_now
On Oct 13, 8:38 am, "Mike Scott" <[EMAIL PROTECTED]> wrote: > Secondly this question has been asked, and solved many times. If you search > through the django-users archives I'm sure you'll find plenty of solutions. > There are solutions out and about in the blogosphere too. Actually I think this is an appropriate place to ask since the resolution (which was unclear) never resulted in action. I was confused about these myself just yesterday because the documentation doesn't mention anything about possible future deprecation. The only action was three months ago with a DeprecationWarning patch that isn't checked in. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: auto_now_add and auto_now
Thierry, Firstly django-developers is not the place for this discussion. Secondly this question has been asked, and solved many times. If you search through the django-users archives I'm sure you'll find plenty of solutions. There are solutions out and about in the blogosphere too. Cheers, Mike. On Mon, Oct 13, 2008 at 10:07 PM, Thierry Stiegler < [EMAIL PROTECTED]> wrote: > > Hi, > > I have a lot of models using this type of fields : > >creation = models.DateTimeField(auto_now_add=True) >update = models.DateTimeField(auto_now=True) > > > But I read that since 2007, it was planned to drop those options from > models.DateField. > > Here the post : > http://groups.google.com/group/django-developers/browse_thread/thread/4cd631c225cb4e52 > > So what I have to do ? New custom fields ? > > I saw some tickets but I didn't find a nice substitute... > > Any suggestions ? > > Yours, > > Thierry. > > > > > > > > > --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
