Changes between Version 2 and Version 3 of Ticket #36371, comment 2
- Timestamp:
- May 6, 2025, 5:12:02 PM (4 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36371, comment 2
v2 v3 1 1 Likely related to tickets such as #31973, #32542. 2 2 3 You possibly have the column your `JSONField` is pointed at defined with a `json` type on Postgres instead of `jsonb` (not something created by Django itself as it never used the `json` type) which [https://github.com/django/django/blob/f7d97dd11819be8996798a7197c5695a317334a0/django/db/backends/postgresql/base.py#L335-L341 the ORM explicitly request not to be deserialized by the backend] to support the `JSONField.decoder` feature. 3 You're likely using Postgres and have the column your `JSONField` is pointed at defined with a `json` type instead of `jsonb` (not something created by Django itself as it never used the `json` type). 4 5 [https://github.com/django/django/blob/f7d97dd11819be8996798a7197c5695a317334a0/django/db/backends/postgresql/base.py#L335-L341 The ORM explicitly request] `jsonb` columns not to be deserialized by the backend (`psycopg2` and `psycopg`) to support the `JSONField.decoder` feature.