Changes between Version 1 and Version 2 of Ticket #32015


Ignore:
Timestamp:
Sep 18, 2020, 12:09:22 AM (4 years ago)
Author:
Mariusz Felisiak
Comment:

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.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #32015

    • Property Component UncategorizedDatabase layer (models, ORM)
    • Property Resolutionduplicate
    • Property Status newclosed
    • Property Summary BUG: psycopg2 json is not loaded with connections.cursorpsycopg2 jsonb is not loaded with connections.cursor
    • Property Type UncategorizedBug
  • Ticket #32015 – Description

    v1 v2  
    44
    55This is also causing issues with a ValuesQuerySet, the output from jsonb fields is always string.
    6 
Back to Top