On Fri, Dec 4, 2009 at 2:48 PM, Alex Gaynor <alex.gay...@gmail.com> wrote: > We will not be adding a setting to pin an application/model to a > specific database. We have already removed the Meta.using option. If > you want to pin an application to a specific database it's fairly > trivial to add a manager and override the save() method to use a > specific DB. Our goal is to design a good long term API for having a > flexible way to define exactly what DB any query goes to, and I > personally have no interest in seeing short term stopgap APIs > implemented.
That's fine for apps under my control, but this leaves us without a way of dealing with 3rd party apps outside of an unfortunate amount of monkey patching. I certainly don't want the API to be "sort term" or "stopgap", but I do want this ability. I don't see any other way to accomplish a heterogeneous admin or partitioning of 3rd party apps. I know and agree with the reasons that the Meta.using option was removed, but it wouldn't have solved these issues either. Adding a key to the DB configs may not be the right way, but I'm sure there is a good way to accomplish this. Thanks, Paul -- 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.
