> When line 7 is uncommented, transaction management is > enabled, and the view works as I would expect.
So it is, my bad, thank you againg. You see, it seemed a little weird, that first (with the decorator) we force transaction to commit manually to use 'test' for all that would happen in our view (suppose that all commits in view should share that 'using' from the decorator), and then explicitly tell the transaction to commit again with 'using'. But if we have transactions to different DBs in one view that seems logical. On 29 апр, 13:16, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Thu, Apr 29, 2010 at 12:20 PM, idle sign <idles...@gmail.com> wrote: > > I'm using the latest trunk fromhttp://github.com/django/django. > > A complete test project you can grab > > athttp://idlesign.narod.ru/django/django-tests.tar.gz > > There is a little bootstrap.sh to run to create DBs. > > > Thank you, Russ. > > Ok - using your test application as provided, I see the "This code > isn't under transaction management" error. That's because line 7 of > views.py (the decorator that enables transaction management) is > commented out. When line 7 is uncommented, transaction management is > enabled, and the view works as I would expect. > > I take it you seeing something different? > > Yours, > Russ Magee %-) > > -- > 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 > athttp://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.
