Re: Oracle testing bug (was Re: Oracle testing issue, looks like bug: Separate connections to same DB)

On Thursday 03 January 2013, Jani Tiainen wrote: > 31.12.2012 14:18, Shai Berger kirjoitti: > > On Sunday 30 December 2012 21:54:52 Anssi Kääriäinen wrote: > >> Seems like you are correct [...]. Please open a bug. > > > > For anyone interested that isn't on the new-bugs list, it's > >

Re: Oracle testing bug (was Re: Oracle testing issue, looks like bug: Separate connections to same DB)

31.12.2012 14:18, Shai Berger kirjoitti: On Sunday 30 December 2012 21:54:52 Anssi Kääriäinen wrote: Seems like you are correct [...]. Please open a bug. For anyone interested that isn't on the new-bugs list, it's https://code.djangoproject.com/ticket/19542 For anyone else: my apologies for

Re: Oracle testing bug (was Re: Oracle testing issue, looks like bug: Separate connections to same DB)

On Sunday 30 December 2012 21:54:52 Anssi Kääriäinen wrote: > > Seems like you are correct [...]. Please open a bug. > For anyone interested that isn't on the new-bugs list, it's https://code.djangoproject.com/ticket/19542 For anyone else: my apologies for the noise. Shai. -- You received

Re: Oracle testing bug (was Re: Oracle testing issue, looks like bug: Separate connections to same DB)

On 30 joulu, 14:20, Shai Berger wrote: > Hi again, > > On Thursday 27 December 2012 15:50:58 Jani Tiainen wrote: > > > There also exists a oldish ticket: > >https://code.djangoproject.com/ticket/14415 > > > That indicates that issue is fixed... > > After looking further into

Re: Oracle testing issue, looks like bug: Separate connections to same DB

Hi again, On Thursday 27 December 2012, Jani Tiainen wrote: > 27.12.2012 15:32, Shai Berger kirjoitti: > > On Thursday 27 December 2012 15:16:15 Jani Tiainen wrote: > >> Just out of curiosity - what's the rationale to duplicate connection > >> information? Why it's so important? > > > > As I

Re: Oracle testing issue, looks like bug: Separate connections to same DB

27.12.2012 15:32, Shai Berger kirjoitti: On Thursday 27 December 2012 15:16:15 Jani Tiainen wrote: Just out of curiosity - what's the rationale to duplicate connection information? Why it's so important? As I noted before, the idea is to use the second connection to write things in a

Re: Oracle testing issue, looks like bug: Separate connections to same DB

On Thursday 27 December 2012 15:16:15 Jani Tiainen wrote: > > Just out of curiosity - what's the rationale to duplicate connection > information? Why it's so important? As I noted before, the idea is to use the second connection to write things in a separate transaction. As the name 'auditlog'

Re: Oracle testing issue, looks like bug: Separate connections to same DB

On Thursday 27 December 2012 15:11:31 Jani Tiainen wrote: > > TEST_MIRROR = 'default' means that instead of creating test database of > "auditlog" using independent database connection Django will reuse > connection to "default". That's how Django makes testing of replication > happen (that's

Re: Oracle testing issue, looks like bug: Separate connections to same DB

27.12.2012 14:41, Shai Berger kirjoitti: Hi Jani and all, On Thursday 27 December 2012 13:28:23 Jani Tiainen wrote: 27.12.2012 13:08, Shai Berger kirjoitti: Hi all, I'm seeing a problem with testing on Oracle, in a setting where there are two defined databases that reference the same

Re: Oracle testing issue, looks like bug: Separate connections to same DB

27.12.2012 14:41, Shai Berger kirjoitti: Hi Jani and all, On Thursday 27 December 2012 13:28:23 Jani Tiainen wrote: 27.12.2012 13:08, Shai Berger kirjoitti: Hi all, I'm seeing a problem with testing on Oracle, in a setting where there are two defined databases that reference the same

Re: Oracle testing issue, looks like bug: Separate connections to same DB

Hi Jani and all, On Thursday 27 December 2012 13:28:23 Jani Tiainen wrote: > 27.12.2012 13:08, Shai Berger kirjoitti: > > Hi all, > > > > I'm seeing a problem with testing on Oracle, in a setting where there are > > two defined databases that reference the same connection parameters > > (this is

Re: Oracle testing issue, looks like bug: Separate connections to same DB

27.12.2012 13:08, Shai Berger kirjoitti: Hi all, I'm seeing a problem with testing on Oracle, in a setting where there are two defined databases that reference the same connection parameters (this is done to enable operations in two parallel, separate transactions); the 'other' database is not

Oracle testing issue, looks like bug: Separate connections to same DB

Hi all, I'm seeing a problem with testing on Oracle, in a setting where there are two defined databases that reference the same connection parameters (this is done to enable operations in two parallel, separate transactions); the 'other' database is not treated as a test database. This means