-
Notifications
You must be signed in to change notification settings - Fork 27
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
find replacement for django-jsonfield #9
Comments
honestly everything is working, so this may be a Django 1.8 kind of thing |
Yeah, I'm thinking jsonb is the way to go here; let's break out once we can land 9.4 and have a solid route to use it. Also, wow, this was the bug we were seeing not to long ago, cc @boblannon |
Closed
closing this as Django 1.9 fixes this in 0.7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
if we want Postgres' JSON we may want to move away, this is a known issue. rpkilby/jsonfield#80
for now I've pinned the jsonfield version to 0.9.20 which doesn't have a problem, but we're getting weird errors on 0.9.22 (on travis) where the JSONField comes back as '{}' instead of {}
The text was updated successfully, but these errors were encountered: