going from 2.2.x to 3.2 is three separate releases of django. That's alot
to go in one jump. Might help if you update one release at a time and
narrow down which version this regression is in.
In addition, I'd check the changelogs for each version and see what, if
any, might apply to your i
Database is postgresql 12
psycopg2-binary==2.8.6 \
The bug occurs when I move from django 2.2.* to 3.2.5
A raw sql query is now behaving differently. A result that was previously
deserialised from a jsonb field into a python dict now returns a string
(and breaks things).
this is a simplifed v
2 matches
Mail list logo
