Thanks Malcom, I suspected this to be the answer, however since I just finished refactoring all of my field references to stop referencing the child model explicitly to give inheritance a try, I was hoping that wouldn't be the case :)
There is one thing about OneToOne fields that isn't exactly equivalent to inheritance, and correct me if I am wrong, you can't ask select_related to go backwards in a relationship. This is critical for my application. On Feb 15, 7:52 pm, Malcolm Tredinnick <[email protected]> wrote: > On Sun, 2009-02-15 at 16:39 -0800, Trey wrote: > > I thought I would ask the question here first before going to devs > > with it. Is it possible to update a model without updating that models > > parent table? > > No. Django doesn't do anything like "damage tracking" to determine which > fields have changed. One day that might well be implemented (there are a > number of different possible approaches, each with benefits and > drawbacks), but until then, no. > > The solution in your case is not to use Python-level inheritance. > Remember that it's only an alternative modelling of an explicit > one-to-one relation. So use an explicit relation and no "chained saving" > will take place (the trade-off being that if you modify the related > model, you'll be responsible for explicitly saving it). > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
