Setting pk should set the related fields also in the base chain.

[Anssi Kääriäinen]

Consider two models:

class A(models.Model):
    pass

class B(A):
    a = models.OneToOneField(A, parent_link=True, primary_key=True)

creating an b instance and setting its pk should also set the a.id:

>>> b = B(pk=1)
>>> b.pk
1
>>> b.a_id
1
>>> b.id
1

At the moment we will get:

>>> b.id is None
True

It would be even better if setting b.id would also set b.a_id, but that is harder to do, and maybe it isn't that important.

[Anssi Kääriäinen]

Made sure to test pk property directly

[Russell Keith-Magee]

This all hinges on a matter of interpretation -- whether you consider the Python object to be a reflection of an actual object, or just a representation of a row in a table.

If the behavior of Django objects was the former, reassigning a primary key would change the primary key of the existing object, in which case, updating primary key values would make sense.

However, the current behavior of Django objects is the latter -- when you reassign the primary key of an object, a new object is created. To my reading, that doesn't automatically imply that any existing objects should follow and point to the new object.

Closing wontfix.