Ticket #12668: multi-db-typos.diff
File multi-db-typos.diff, 1.3 KB (added by , 15 years ago) |
---|
-
docs/topics/db/multi-db.txt
149 149 object instance that is related to the read or write operation that is 150 150 underway. This might be the instance that is being saved, or it might 151 151 be an instance that is being added in a many-to-many relation. In some 152 cases, no instance hint will be provided at all. The router check for153 the existence of an instance hint, and determine if hat hint should be152 cases, no instance hint will be provided at all. The router checks for 153 the existence of an instance hint, and determine if that hint should be 154 154 used to alter routing behavior. 155 155 156 156 Using routers … … 192 192 doesn't provide any solution for handling replication lag (i.e., 193 193 query inconsistencies introduced because of the time taken for a 194 194 write to propagate to the slaves). It also doesn't consider the 195 interaction of transactions with the database utiliz tion strategy.195 interaction of transactions with the database utilization strategy. 196 196 197 197 So - what does this mean in practice? Say you want ``contrib.auth`` to 198 198 exist on the 'credentials' database, and you want all other models in a