On Sun, 2009-02-15 at 20:41 -0500, Alex Gaynor wrote:
[...]
>
> select_related doesn't traverse the reverse relation from inheritance
> either, there's a ticket about this:
> http://code.djangoproject.com/ticket/7270 in any event, how can your
> application depend on that, select_related
On Sun, Feb 15, 2009 at 8:38 PM, Trey wrote:
>
> 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 :)
>
>
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 e
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
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?
A very small example:
class Aye(model):
a = field
class Bee(Aye):
b = field
o = Bee.objects.get(k)
o.b = 3
o.save()
In my code this will
5 matches
Mail list logo
