Skip to content

Fixed #35453 -- ManyToManyField no longer flagged as a concrete field. #19602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rpkilby
Copy link

@rpkilby rpkilby commented Jun 27, 2025

Trac ticket number

ticket-35453

Branch description

Per discussion in PR #19595, ManyToManyField is likely misidentified as concrete. 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

  • This PR targets the main branch.
  • The commit message is written in past tense, mentions the ticket number, and ends with a period.
  • I have checked the "Has patch" ticket flag in the Trac system.
  • I have added or updated relevant tests.
  • I have added or updated relevant docs, including release notes if applicable.
  • I have attached screenshots in both light and dark modes for any UI changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant