Re: Testing multidb without inconsistency

2012-02-25 Thread Anssi Kääriäinen
On Feb 25, 10:31 am, Jeremy Dunck wrote: > On Sat, Feb 25, 2012 at 2:13 AM, Anssi Kääriäinen > > wrote: > > I think you really should use a transactional test case. The reason is > > that before you do a commit, your writes really should not be visible. > > Hiding this in testing could lead to hi

Re: Testing multidb without inconsistency

2012-02-25 Thread Jeremy Dunck
On Sat, Feb 25, 2012 at 2:13 AM, Anssi Kääriäinen wrote: > On Feb 25, 9:24 am, Jeremy Dunck wrote: >> I have a master and a replica.  In test, the TEST_MIRROR on the >> replica points to master.  I make writes to master, then read from >> replica, then assert some numbers. >> ... > I think you re

Re: Testing multidb without inconsistency

2012-02-25 Thread Anssi Kääriäinen
On Feb 25, 9:24 am, Jeremy Dunck wrote: > I have a master and a replica.  In test, the TEST_MIRROR on the > replica points to master.  I make writes to master, then read from > replica, then assert some numbers. > > def test_stuff(self): >     Foo.objects.using('master').create() >     number_rece

Testing multidb without inconsistency

2012-02-24 Thread Jeremy Dunck
I have a master and a replica. In test, the TEST_MIRROR on the replica points to master. I make writes to master, then read from replica, then assert some numbers. def test_stuff(self): Foo.objects.using('master').create() number_received = do_expensive_computations() # Down in some