Change token field type from CharField to TextField in AbstractRefres… #1558
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hToken model for improved storage capacity.
for more information, see https://pre-commit.ci
|
TextFields are not searchable for certain database backends. This feels like something recently discussed in another PR. |
|
See #1447 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #1557
Description of the Change
This pull request changes the
AbstractRefreshTokenmodel indjango-oauth-toolkitby updating thetokenfield from aCharFieldto aTextField. This modification allows for greater storage capacity and prevents thedjango.db.utils.DataErrorcaused by exceeding the character limit (255) for theCharField.By switching to
TextField, we ensure that the refresh token can accommodate larger values, which may be needed as token sizes or encoding formats evolve.Checklist
This PR should resolve the token size issue. Let me know if you need any further adjustments to the description or additional information!