Skip to content
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

Documentation: Migrating to the builtin JSONField in newer versions of Django #255

Open
anrie opened this issue Aug 11, 2020 · 5 comments
Open

Comments

@anrie
Copy link

anrie commented Aug 11, 2020

Hey!

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?

@matteing
Copy link

+1

1 similar comment
@pymen
Copy link

pymen commented Aug 12, 2021

+1

@cbporch
Copy link

cbporch commented Feb 3, 2022

How would the migration path look like in case you are already using django-jsonfield and want to change to the builtin version?

Just wanted to clarify, since I'm also looking into swapping to the built-in field: django-jsonfield is not the library contained in this repo.

@tserrien
Copy link

Some guide or example project would still be very much appreciated! I'm using this package and not django-jsonfield.

@jeffbowen
Copy link

FWIW, I was on Django 3.2.24 and simply switched to using the built-in models.JSONField and removed the jsonfield import/requirement. No migration necessary. Everything seems to be working fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants