Re: Custom manager and delete()

I manage to do row delete operations. Not very nice, since there's no delete-related, no signalst etc. I don't think delete can be fixed for multiple databases without modifying Django source or without duplicating code. Since delete_objects function uses the global connection variable. Would be

Re: Custom manager and delete()

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).

Re: Custom manager and delete()

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

Custom manager and delete()

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 t