Re: [Django] #27288: In multi-db setup changes written to master are not seen on read-replicas

[Django]

#27288: In multi-db setup changes written to master are not seen on 
read-replicas
---+--
 Reporter:  Jose M Herrero |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Testing framework  |  Version:  1.10
 Severity:  Normal |   Resolution:  invalid
 Keywords:  multi-db dbrouter  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Simon Charette):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 It looks like you didn't set the
 
[https://docs.djangoproject.com/en/1.10/topics/testing/tools/#django.test.TransactionTestCase.multi_db
 multi_db attribute] on your test case class.

 Please don't use the ticket system as a support channel, see
 [wiki:TicketClosingReasons/UseSupportChannels].

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.b7ac93f2dd51f133abb22938fceed6c5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27288: In multi-db setup changes written to master are not seen on read-replicas

[Django]

#27288: In multi-db setup changes written to master are not seen on 
read-replicas
---+--
 Reporter:  Jose M Herrero |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Testing framework  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords:  multi-db dbrouter  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Jose M Herrero):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Using `TransactionTestCase' solves the problem, maybe multi-db in tests is
 only intended to test that replication configuration works and not the
 whole set of tests?

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ec9dec5ef3ecfac886476ad44d37a434%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.