#30690: get_or_create() ignores database router's db_for_read() method
     Reporter:  Maciej Olko          |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  closed
    Component:  Database layer       |                  Version:  2.2
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  duplicate
     Keywords:  router, database-    |             Triage Stage:
  router, get_or_create              |  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:   => duplicate


 By it's nature or dealing with both read and writes the `get_or_create`
 method '''has''' to be targeting the ''write'' database for reads.

 There's a comment in the method definition about it]  and following the
 `git blame` trace leads to
 this commit].

 Closing as duplicate of #16865.

Ticket URL: <https://code.djangoproject.com/ticket/30690#comment:1>
Django <https://code.djangoproject.com/>
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 view this discussion on the web visit 

Reply via email to