Skip to content

refactor: warning not handle attribute changes with field name #509

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.

Sign up for GitHub

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

Jump to bottom
Merged
waketzheng merged 2 commits into from
Nov 11, 2025
Merged

refactor: warning not handle attribute changes with field name #509

waketzheng merged 2 commits into from
Nov 11, 2025

Conversation

@waketzheng
Copy link
Contributor

@waketzheng waketzheng commented Nov 10, 2025

Description

It's better to show changes of which field was ignored, e.g.:

  • Currently
Aerich does not handle 'unique' attribution for m2m field. You may need to change the constraints in db manually.
  • After PR merged
Aerich does not handle 'unique' attribution for m2m field(models.Users.friends). You may need to change the constraints in db manually.

@waketzheng waketzheng merged commit 93c523e into tortoise:dev Nov 11, 2025
34 checks passed
@waketzheng waketzheng deleted the refactor-warning-which-field branch November 12, 2025 05:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@waketzheng