-
Notifications
You must be signed in to change notification settings - Fork 79
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
Convert most CharField instances to TextField #532
Labels
Comments
hstct
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Jun 1, 2022
hstct
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Jun 1, 2022
hstct
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Jun 2, 2022
hstct
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Jun 2, 2022
hstct
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Jun 13, 2022
hstct
added a commit
to ATIX-AG/pulp_deb
that referenced
this issue
Jun 13, 2022
quba42
pushed a commit
that referenced
this issue
Jun 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There now seems to be a consensus for both pulpcore and pulp_rpm, that TextField is always better than CharField for Pulp.
I gather this is because of how PostgreSQL implements these two fields on the DB side.
For consistency pulp_deb should also follow suit.
See: pulp/pulp_rpm#2515 as a reference.
The text was updated successfully, but these errors were encountered: