On Tue, 3 Feb 2015 19:38:31 -0500 Larry Martell <larry.mart...@gmail.com> wrote:
> I have a django app that uses a temp table. In the real world this is > no issue, as each invocation of the app runs in its own MySQL session > so there cannot be any conflict with the temp tables. But in my tests > there are multiple requests sent, and apparently they are all in the > same session, as on the second request I get an error because the temp > table already exists. I tried logging out between requests, and I > tried creating a new Client instance for each request, but I still got > the error. Then I tried deleting the Client object, but I got Client > object has no attribute __del__. > > What I can do so that each request in a test has its own MySQL session? Instead of Django standard TestCase (which internally wraps all in single transaction and makes transactions as a no-op), you should use TransactionalTestCase. https://docs.djangoproject.com/en/1.7/topics/testing/tools/#transactiontestcase -- Jani Tiainen -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/20150205142945.6569122d%40jns42-l.w2k.keypro.fi. For more options, visit https://groups.google.com/d/optout.
