We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Inyoka has a custom JSONField Basically, this will work.
However, Django offers nowadays an own JSONField:
Migrating to Django's one could save maintenance (in the longterm) and make queries easier. However, it is unclear, how much work it is to migrate.
The text was updated successfully, but these errors were encountered:
Does our own JSONField use the DB native column types, or just TEXT with a JSON in it?
TEXT
Sorry, something went wrong.
hm, seems like the line number where the class is located changed
inyoka/inyoka/utils/database.py
Line 153 in 7de28b0
At the moment it's only a Textfield with Python's json.loads(s) and json.dumps(obj, cls=DjangoJSONEncoder).
json.loads(s)
json.dumps(obj, cls=DjangoJSONEncoder)
No branches or pull requests
Inyoka has a custom JSONField Basically, this will work.
However, Django offers nowadays an own JSONField:
Migrating to Django's one could save maintenance (in the longterm) and make queries easier. However, it is unclear, how much work it is to migrate.
The text was updated successfully, but these errors were encountered: