-
Notifications
You must be signed in to change notification settings - Fork 61
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
Migrate JSONField to Django builtin JSONField #919
Conversation
This runs a migration that converts from text to jsonb. In my local testing it converted the field properly: ``` ethicaladserver=# select targeting_parameters from adserver_flight; targeting_parameters ---------------------------- { + "niche_targeting": 0.9+ } (1 row) ethicaladserver=# select targeting_parameters from adserver_flight; targeting_parameters -------------------------- {"niche_targeting": 0.9} (1 row) ```
0dbf98c
to
01c322e
Compare
01c322e
to
680799b
Compare
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.
Not sure what the deal is with simple history, but sans that this looks good.
I'll take a look at this and see if I can't resolve the issue. |
The test failures seem to be a result of jazzband/django-simple-history#1181 which is still open. We may have to either ignore historical changes on jsonfields, stop adding a change reason (remove calls to |
FWIW, I never look at |
This is a temporary fix until the underlying issue is fixed.
I created a PR #924 to remove |
Cool. Let's plan to get it merged and deployed next week. 👍 |
…change-reason-removal Remove simple history change reason
This runs a migration that converts from text to jsonb.
In my local testing it converted the field properly: