Django 3.2 LTS
One line description of the issue
When I use Django 3.2 LTS i have a fetchmany DatabaseError so I cannot use djongo as my NoSQL database and postgres as RDBMS which is needed. Can we all agree that this needs to be updated? Also, it would be nice to have an option to allow both types of databases with a given router or something. Djongo is fantastic and with this is even better. Without this, we need to adopt different solutions which I would like to avoid.
@rudolfce Anything to say about djongo throwing Database Error (Exception Location: ....cursor.py, line 70, in fetchmany)?
Does Djongo work on Django 3.2 LTS already? Django 3.1 is no longer being updated. Can I update to 3.2 LTS or do I have to downgrade to 2.2 LTS in order to receive security fixes?
