Adam Johnson

So I've just realized I've confused *column* checks and *table* checks. Django already supports column checks - retrieved from https://github.com/django/django/blob/master/django/db/models/fields/__init__.py#L667 - and seems to apply them even on backends where...

@diedoman until this issue is closed, JSONField is only supported on MySQL 5.7. You can always use `SILENCED_SYSTEM_CHECKS` and use it in 'unsupported' mode - it won't be enforcing JSON...

I started a branch to work on this back in November-ish, I found the same problem you're reporting. I will have another look at Djangocon EU this week.

Afraid not, if there was it would be here.

There's no update, again if there was it would be here. I have limited time to work on open source. From my initial experimetns, I recall this could require a...

I don't have time to work on this right now (at least unpaid). My main vision would be to spend time getting the universal JSONField merged to Django core. After...

@ronaldchoi [The JSONField docs state](https://django-mysql.readthedocs.io/en/latest/model_fields/json_field.html): > This field requires Django 1.8+ and MySQL 5.7+. I'd accept a PR adding a sentence to the installation instructions that not all features are...

Django 3.1 in beta has a univresal JSONField, the dev who made it is working on a backport package: https://twitter.com/laymonage/status/1278485132765085696

N.B. Django 2.0 doesn't support MySQL 5.5 any more, so it's tempting not to do this.

Yes sure!