Fixed #35453 -- ManyToManyField no longer flagged as a concrete field. #19602
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.
Trac ticket number
ticket-35453
Branch description
Per discussion in PR #19595,
ManyToManyField
is likely misidentified asconcrete.
The is fixed by removing the non-existent column name from the field. This also removes the now redundant(field.is_relation and field.many_to_many)
check and updates the field error to more explicitly point out that fields must be concrete.There are several failures in the schema and migrations tests.
Checklist
main
branch.