Ticket #12668: multi-db-typos.diff

File multi-db-typos.diff, 1.3 KB (added by mattimustang, 5 years ago)
  • docs/topics/db/multi-db.txt

     
    149149object instance that is related to the read or write operation that is
    150150underway. This might be the instance that is being saved, or it might
    151151be 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 for
    153 the existence of an instance hint, and determine if hat hint should be
     152cases, no instance hint will be provided at all. The router checks for
     153the existence of an instance hint, and determine if that hint should be
    154154used to alter routing behavior.
    155155
    156156Using routers
     
    192192    doesn't provide any solution for handling replication lag (i.e.,
    193193    query inconsistencies introduced because of the time taken for a
    194194    write to propagate to the slaves). It also doesn't consider the
    195     interaction of transactions with the database utiliztion strategy.
     195    interaction of transactions with the database utilization strategy.
    196196
    197197So - what does this mean in practice? Say you want ``contrib.auth`` to
    198198exist on the 'credentials' database, and you want all other models in a
Back to Top