Opened 4 years ago
Last modified 4 years ago
#32015 closed Bug
BUG: psycopg2 json is not loaded with connections.cursor — at Version 1
| Reported by: | Matt Buck | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 3.1 |
| Severity: | Normal | Keywords: | psycopg2, database, postgresql, json, jsonb, jsonfield |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Since the upgrade from v3->v3.1, I discovered this regression in the psycopg2 cursor. jsonb results from sql queries are not loaded into python data structures. This causes issues when dumping and loading again, the json fields do not get loaded on the front. The offending line of code can be found here https://github.com/django/django/blob/master/django/db/backends/postgresql/base.py#L206 in the postgresql backend.
This code was introduced to work around issues with specifying a JSONDecoder in the new JSONField. Attempting to implement a workaround by creating additional connections sort of works, but causes freezing during cleanup of test cases, and maybe more serious issues elsewhere.
This is also causing issues with a ValuesQuerySet, the output from jsonb fields is always string.