Re: Tests and temp tables

On Thu, Feb 5, 2015 at 3:16 PM, Carl Meyer wrote: > On 02/05/2015 11:20 AM, Larry Martell wrote: >> On Thu, Feb 5, 2015 at 10:53 AM, Carl Meyer wrote: >>> TransactionTestCase has been around for quite a long time (since 1.1, >>> IIRC). It's definitely in 1.5.

Re: Tests and temp tables

On 02/05/2015 11:20 AM, Larry Martell wrote: > On Thu, Feb 5, 2015 at 10:53 AM, Carl Meyer wrote: >> TransactionTestCase has been around for quite a long time (since 1.1, >> IIRC). It's definitely in 1.5. > > I thought it was not in 1.5 because I went to >

Re: Tests and temp tables

On Thu, Feb 5, 2015 at 10:53 AM, Carl Meyer wrote: > Hi Larry, > > On 02/05/2015 06:57 AM, Larry Martell wrote: >> On Thu, Feb 5, 2015 at 7:29 AM, Jani Tiainen wrote: >>> On Tue, 3 Feb 2015 19:38:31 -0500 >>> Larry Martell wrote: >>>

Re: Tests and temp tables

Hi Larry, On 02/05/2015 06:57 AM, Larry Martell wrote: > On Thu, Feb 5, 2015 at 7:29 AM, Jani Tiainen wrote: >> On Tue, 3 Feb 2015 19:38:31 -0500 >> Larry Martell wrote: >> >>> I have a django app that uses a temp table. In the real world this is >>>

Re: Tests and temp tables

On Thu, Feb 5, 2015 at 7:29 AM, Jani Tiainen wrote: > On Tue, 3 Feb 2015 19:38:31 -0500 > Larry Martell 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

Re: Tests and temp tables

On Tue, 3 Feb 2015 19:38:31 -0500 Larry Martell 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

Tests and temp tables

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