On 1/21/06, hugo <[EMAIL PROTECTED]> wrote: > So I am +1 on that change,
I've attached an alternate version of the patch that implements this idea. In this version, the object instance defers to the default manager for delete functionality. This removes the duplication of SQL delete logic, but it opens a different box of problems in identifying the correct manager. Having a quick poke around, it looks like it should be reasonably easy to move all SQL related calls from the Model to the Manager in a similar way, as long as you can identify the manager on which to make the call. The default manager works fine for the simple case, but how do propose to choose the 'correct' manager if there are multiple managers involved? Russ Magee %-)
