Hi Russell, Thanks, I'm rather happy too. It's exactly what we wanted!
DB Routing API is even better than some fixed db routing format. I just thought about any model with GFK, like TagField from django-tagging -- with multidb, to be effectively reusable, it has to know in what DB to save and load, depending on its client ContentType. Since it's solution for the problems discussed in http://groups.google.com/group/django-developers/browse_frm/thread/7904c7da7cb0085f/d063d2086299635e, could you please think about one more thing discussed there: syncdb targeting to correct databases. Something like a db_router.get_all_databases_for_model(model) call. It was suggested in the thread. Another issue is bothering me: db_router.allow_relation doesn't convert in my head into any algorithm of its usage. Docs in this thread didn't help me either when it's called and what for. So I took a look into implementation, it looks like it only works as a validator: ...if not router.allow_relation(obj, self.instance): raise ValueError(...) But how one would suggest in which db to save object depending on the related object? I.e., let's talk about this example with GFK. Thanks! On Wed, Jan 20, 2010 at 10:06 PM, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > Ok - so that's the patch. Any comments, queries, or criticisms are welcome. > > Yours, > Russ Magee %-) -- Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, MSN: bu...@live.com
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
