-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
fix: #51842 #52553
fix: #51842 #52553
Conversation
minion_fn = models.CharField() | ||
user_fk = models.ForeignKey(User, on_delete=models.CASCADE) | ||
minion_or_fn_matcher = models.CharField(max_length=255) | ||
minion_fn = models.CharField(max_length=255) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there's an assumption of Postgres as the database, there's no reason to add max_length.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah... I see it's required in Django's CharField
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apparently one needs to make their own CharField
to avoid Django's limit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mattLLVW Is it possible to add a test for this change?
It's a documentation change...? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mattLLVW My bad I took a glance and it looked like a code change. Approved.
What does this PR do?
Fix #51842 Wrong model name
What issues does this PR fix or reference?
#51842