🐞 Fix ProgrammingError à cause du champ id manquant dans les modèles Ica_ sans primary_key #1573
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dans 1482, j'ai modifié les modèles générés automatiquement par un
inspectdb
qui faisaient porter la contrainteprimary_key=True
sur un champ unique au lieu que ce soit une primary_key composite.Les primary_key composites n'existent pas avec Django.
Mais en supprimant cette contrainte Django cherche un champ primary_key par défault
id
qui n'existe pas dans la table ->ProgrammingError
Comme c'est un modèle unmanaged, alors l'incohérence entre les contraintes réelles dans PostgreSQL et les modèles Django ne sont pas impactantes.