I'm following you now. I was reading through the transaction.py code after David's post, and had just come to the same conclusion.
I have a function (called in a loop) that contains all my model get's and saves, so I tried the commit_on_success decorator. Sadly, the next database interaction after the failing save, which is a get in the beginning of the function on the next time through the loop, fails with: current transaction is aborted, commands ignored until end of transaction block Perchance I also need to create a savepoint and do savepoint_rollback? Bill On Thu, Apr 15, 2010 at 11:03 AM, Thomas Guettler <h...@tbz-pariv.de> wrote: > > > Bill Freeman wrote: >> How does this apply when there is no request? I'm not following you. > > I forgot to say, that I would create a temporary script file which > uses the decorator commit_on_success instead of using "manage.py shell". > > Thomas > > > -- > Thomas Guettler, http://www.thomas-guettler.de/ > E-Mail: guettli (*) thomas-guettler + de > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
