You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Considering the advice to eventually use Django's builtin JSONField:
If you're an end user of PostgreSQL and want full-featured JSON support, then it is recommended that you use the built-in JSONField.
How would the migration path look like in case you are already using django-jsonfield and want to change to the builtin version?
Is it simply possible to transparently swap the field and go with Django's proposed AlterField migration or are there any gotchas and things to consider?
The text was updated successfully, but these errors were encountered:
Hey!
Considering the advice to eventually use Django's builtin
JSONField
:How would the migration path look like in case you are already using
django-jsonfield
and want to change to the builtin version?Is it simply possible to transparently swap the field and go with Django's proposed
AlterField
migration or are there any gotchas and things to consider?The text was updated successfully, but these errors were encountered: