#4257 (ContentType ordering is not always the same)

by Luc Saffre · in Developers · assigned to Luc Saffre

Résumé

The docs/specs/gfks.rst test fails in book (probably since I changed that page from min2 to min9, which has more models) because households.Member and households.Household get a different pk on my machine and on GitLab.

Concepts sous-jacents

Commentaires

5 ans, 3 mois ago by Luc Saffre about #4257 (ContentType ordering is not always the same) : I moved a section about help_texts from that file to docs/dev/help_texts.rst (anyway this is a better place for this section) and changed specs/gfks.rst back to use min2 where we have less models an therefore the issue doesn't occur.
5 ans, 3 mois ago by Luc Saffre about #4257 (ContentType ordering is not always the same) : I knew it: "Since ContentType objects are automatically created by Django during the database synchronization process, the primary key of a given content type isn’t easy to predict; it will depend on how and when migrate was executed." (found [url django.fun/docs/django/en/3.1/topics/serialization/ ...
5 ans, 3 mois ago by Luc Saffre about #4257 (ContentType ordering is not always the same) : Theoretically this is not a problem because restore.py doesn't rely on CT staying the same. But still it's hounting...