I am unsure if this a bug in Django, or django-multidb-router, or something I've done wrong.
I'm using django-multidb-router from here: http://github.com/jbalogh/django-multidb-router With two database definitions, a read_only_user and a read_write_user (with the intentions of having multiple read-only definitions) As far as I can tell, all reads get directed to the read_only_user and all writes get detected to read_write_user. That is, until contrib.Admin tries to create a new user message for a save() which for tries to write with the read_only_user and fails. When overriding auth.Message.save() with an empty function, the admin interface resumes working as expected, with reads and writes being sent to the appropriate databases. >From what I guess by looking at the traceback, `RelatedManager` is overriding `get_query_set()` to set the query-set's DB. But when the `create()` call gets down to `models.query.QuerySet.create()`, `obj.save()` (line 350) is called, and forces `using` to self.db, negating any direction from the Router. Can anybody confirm it's a Django bug? Cheers, -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
