Changes between Initial Version and Version 1 of Ticket #13724, comment 2


Ignore:
Timestamp:
07/20/13 22:52:28 (9 years ago)
Author:
Paul Collins
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13724, comment 2

    initial v1  
    11So we're not using the django-multidb-router, and we're seeing this kind of odd behavior as well. Allow_relation is not being called, which makes sense but what doesn't make sense is
    2 ```
    3 .all().delete()
    4 ```
     2`.all().delete()`
    53The Router is being called for the .all() (db_for_read), but then the QuerySet is being changed to a DELETE. Since db_for_write is never  called, and our router automatically picks a read-only slave for read-only queries, thus the expected explosion happens.
Back to Top