Current documentation says that when we break a model down into parts, and we need to define the partsPKs explicitly, we can use eitherIntegerFieldorAutoField; it even prefers IntegerField` because these fields should, in principle, not have generated values put into them (they should have values copied from those generated for the main model), and that is a little more explicit.
However, this creates issues with the Django admin -- IntegerFields show up as editable, and even required, in the admin for the main model. Changing them to AutoField makes them go away, and probably sets some other things straight (e.g. marks them as serialized=False).
The documentation needs to be changed.
Current documentation says that when we break a model down into parts, and we need to define the parts
PKs explicitly, we can use eitherIntegerFieldorAutoField; it even prefersIntegerField` because these fields should, in principle, not have generated values put into them (they should have values copied from those generated for the main model), and that is a little more explicit.However, this creates issues with the Django admin --
IntegerFields show up as editable, and even required, in the admin for the main model. Changing them toAutoFieldmakes them go away, and probably sets some other things straight (e.g. marks them asserialized=False).The documentation needs to be changed.