psycopg2 jsonb is not loaded with connections.cursor

[Matt Buck]

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.

[Mariusz Felisiak]

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 is an intended change, see #31991.

This causes issues when dumping and loading again, the json fields do not get loaded on the front.

I cannot reproduce any issue with dumpdata/loaddata.

This is also causing issues with a ValuesQuerySet, the output from jsonb fields is always string.

Using QuerySet.values() works for me.

Duplicate of #31991. I'm happy to reopen if you can provide a sample project that reproduce described issues with builtin mechanisms.