Django 4.2 fixes #28
Closed
Django 4.2 fixes #28
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
benthuffine
approved these changes
Jul 25, 2023
|
|
||
| # Verify that the value that was stored in the database was a json null, i.e. a string with the value 'null' | ||
| # NO! That is NOT what we want! If the field is nullable, we should store a real null. | ||
| # dbvalk = get_field_value('nulltruemodel', 'k') |
There was a problem hiding this comment.
Remove commented code.
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.
Django 4.2 weirdly changes some of how JSONField works. It even seems like maybe a bug, at least a discrepancy from their documentation. These changes address that.