#32135: JSONField db_type `jsonb`==>`json` for sequential data no longer works
-------------------------------------+-------------------------------------
Reporter: Michael Anuzis | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
* component: Uncategorized => Database layer (models, ORM)
Comment:
> Is there a reason json was permitted via workaround in 3.0 and
forcefully disabled in 3.1?
Using `json` data type was never supported.
`django.contrib.postgres.fields.JSONField` in Django > 3.1 also uses
`jsonb` (see related #30476).
--
Ticket URL: <https://code.djangoproject.com/ticket/32135#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.5b9a9d9cdd0160bd37583ea3b4a19c63%40djangoproject.com.
