Just as a follow-up. I ended up switching to Elixir to handle my multiple legacy databases, while keeping django to handle the main system. The syntax is very similar, and it provides some additional flexibility that allows me to deal with those legacy DB's (like dealing with non-indexed tables).
I hope to revert back to full django ORM, once it has multi-db support. Michael. Adi Andreias wrote: > Hello, > > Anyone can give us a hint with this? > I have the same problem: with a custom manager (for a 2nd database) > SELETs and INSERTs are working, but not the DELETE operation. > Seems like DELETE references a global connection variable (to the main > database). > > Thanks > > > michael wrote: > >> Hi, >> >> [Sorry, if this has been asked before] >> I defined a model using a custom manager. However, this custom manager >> is not used when I call "delete()" method on an instance object. The >> reason >> I use a custom manager is because the model represents objects in >> another >> legacy database (different from the normal database used by django). >> So >> I'm basically trying to emulate multi-db support. >> >> Obviously, as delete() uses the default manager, it fails as the >> corresponding >> table is not in that database. >> >> Is there a workaround for this, or do I have to overload delete() in >> my model >> and use raw SQL? >> >> Thanks, >> Michael. >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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 -~----------~----~----~----~------~----~------~--~---
