Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

MySQL users will have no alternative when support for JSONField is dropped

See original GitHub issue

I noticed that the current docs say the following with respect to django-extensions’s JSONField:

Deprecated since version 1.7.3: Django 1.9 features a native JSONField. Django-Extensions will support JSONField at the very least until Django 1.8 becomes unsupported.

Ref: https://django-extensions.readthedocs.io/en/latest/field_extensions.html#current-database-model-field-extensions

However, the JSONField provided by Django is for PostgreSQL only. Ref: https://docs.djangoproject.com/en/1.11/ref/contrib/postgres/fields/#jsonfield

Thus, when django-extensions drops support for JSONField, users of MySQL and other database backends will not have an alternative field that they can migrate to. Shouldn’t support for this field be reconsidered?

Thank you for your time!

Issue Analytics

State:
Created 6 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

3reactions

trbscommented, May 31, 2017

I’m happy to leave it in as long as there are (enough) users that find it useful.

Maybe we should improve the documentation instead of deprecating it. Make it very clear in the docs that alternatives exists like the build-in JSONField when using PostGreSQL and maybe some of the other implementations out there which might be better supported.

Of course everybody is happy to use our version 😃

0reactions

trbscommented, Jun 2, 2017

Thanks !