Comments on: Django auto_now Removal Gotcha http://coderseye.com/2007/django-auto_now-removal-gotcha.html Programming is passion made real Fri, 09 Dec 2011 00:27:29 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: Bass Guitar Stands http://coderseye.com/2007/django-auto_now-removal-gotcha.html#comment-359 Bass Guitar Stands Thu, 27 May 2010 07:20:39 +0000 http://coderseye.com/2007/django-auto_now-removal-gotcha.html#comment-359 Nice to be visiting your blog again, it may be months for me. Well this post that i've been waited for so long. I need this post to total my assignment in the college, and it has exact same topic with your article. Many thanks, excellent write about. Nice to be visiting your blog again, it may be months for me. Well this post that i’ve been waited for so long. I need this post to total my assignment in the college, and it has exact same topic with your article. Many thanks, excellent write about.

]]> By: Ramin http://coderseye.com/2007/django-auto_now-removal-gotcha.html#comment-358 Ramin Sun, 24 Feb 2008 18:03:04 +0000 http://coderseye.com/2007/django-auto_now-removal-gotcha.html#comment-358 Minor typo. models.DatetimeField() should be models.DateTimeField() (with capitalized 'T'). Minor typo.

models.DatetimeField() should be models.DateTimeField() (with capitalized ‘T’).

]]> By: Malcolm Tredinnick http://coderseye.com/2007/django-auto_now-removal-gotcha.html#comment-357 Malcolm Tredinnick Tue, 08 May 2007 01:53:15 +0000 http://coderseye.com/2007/django-auto_now-removal-gotcha.html#comment-357 There's something else going on here, I suspect. Both the create() and get_or_create() method do call your model's save() method. In fact, get_or_create() is implemented more or less exactly as in your second example. If you want to trace throught the code, MyModel.objects.get_or_create() calls django.db.models.manager.Manager.get_or_create() which just passes off the real work to django.db.models.query.QuerySet.get_or_create() and you can see that calling obj.save() when required. So it would be interesting to understand what is really changing when you make the substitution you suggest above. There’s something else going on here, I suspect. Both the create() and get_or_create() method do call your model’s save() method. In fact, get_or_create() is implemented more or less exactly as in your second example.

If you want to trace throught the code, MyModel.objects.get_or_create() calls django.db.models.manager.Manager.get_or_create() which just passes off the real work to django.db.models.query.QuerySet.get_or_create() and you can see that calling obj.save() when required.

So it would be interesting to understand what is really changing when you make the substitution you suggest above.

]]>