ATV-172 Fix content formatting when saving to db #84
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
Override get_db_prep_save to create a json formatted string instead of psycopg2 Json object
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.
Override get_db_prep_save to create a json formatted string instead of psycopg2 Json object
Description ✨
Content has to be saved in exactly the same way as before Django update to maintain data integrity
Issues 🐛
Closes 🙅♀️
ATV-172: Fix content format when saving to DB
Related 🤝
Testing ⚗️
Automated tests ⚙️️
No
Manual testing 👷♂️
Yes
Screenshots 📸
Additional notes 🗒️