I think therefore you could resolve the issue by doing save(update_fields=['count']) in your code.
On 15 January 2015 at 06:31, Horacio G. de Oro <[email protected]> wrote: > Yeap. Removing the save() done in <A> solved the issue. > > And some component is doing and update() - not a save(). I see in the > Postgresql logs an UPDATE of the hash with the new increment, that includes > only the "password" field. > > I thought that autenticate() produced a read operation on the DB... now I > know that it's read/write! > > So, it's not a Django issue :-) > > Thanks! > Horacio > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/3cfce232-a561-4c79-8728-8f33548d2cf3%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/3cfce232-a561-4c79-8728-8f33548d2cf3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1H670%2BtBM%3Dd2CVRUFnArR%3DwoeZB-gOHE7g6NPu_pOjHjg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
