Context Navigation

Changes between Initial Version and Version 1 of Ticket #23718, comment 23

initial	v1
1		Hi Team,
2
3		We also noticed an issue here which happens when you have a default + read_replica config, and you have a router that only selects a read_replica when considering particular models. If you have those conditions, _and_ a data migration that uses both Job and User, you will have issues because the "default" connection config will be pointing to your `test_myschema`, whereas the `read_replica` config will still be pointing to `myschema`.
	1	My team at work also noticed an issue here which happens when you have a default + read_replica config, and you have a router that only selects a read_replica when considering particular models. If you have those conditions, _and_ a data migration that uses both Job and User, you will have issues because the "default" connection config will be pointing to your `test_myschema`, whereas the `read_replica` config will still be pointing to `myschema`.
4	2
5	3	e.g.,