Re: Suspected bug: testing with multiple references to same database

2010-10-10 Thread Russell Keith-Magee
2010/10/11 Filip Gruszczyński : > I am not very familiar with all this, but I took a look at the code > and have a question. Would it be enough to make a following validation > before setting up test databases: for each two connections using the > same backend names of the test databases are differ

Re: Suspected bug: testing with multiple references to same database

2010-10-10 Thread Filip Gruszczyński
I am not very familiar with all this, but I took a look at the code and have a question. Would it be enough to make a following validation before setting up test databases: for each two connections using the same backend names of the test databases are different? -- Filip Gruszczyński -- You re

Re: Suspected bug: testing with multiple references to same database

2010-10-07 Thread Shai Berger
On Thursday 07 October 2010 07:31:49 Russell Keith-Magee wrote: > > It certainly sounds to me like a legitimate bug (or group of bugs). > It is now bug #14415. Thanks, Shai. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post

Re: Suspected bug: testing with multiple references to same database

2010-10-06 Thread Russell Keith-Magee
On Thu, Oct 7, 2010 at 1:57 AM, Shai Berger wrote: > Hi all, > > I am developing an application which needs to write an audit log to a > database. I want the committing of log records to be independent of the > committing of other database writes (so user actions can be audited even if > they caus

Suspected bug: testing with multiple references to same database

2010-10-06 Thread Shai Berger
Hi all, I am developing an application which needs to write an audit log to a database. I want the committing of log records to be independent of the committing of other database writes (so user actions can be audited even if they cause errors). So I figured the easiest way to do so would be to