Description:
The newer version of Django was resulting in the psycopg2.errors.InvalidCursorName as certain functionality has been changed in newer versions. Viewing the documentation and stackoverflow links I realized that this is a known issue while upgrading to the latest version of Django. However, the version of Django we were previously using, 3.2.* the minor version is still compatible with python 3.10.13 so reverted back to that and the error resolved itself.
Technical details:
The technical details for the knowledge of other developers. Any detailed caveats or specific deployment steps should be outlined here.
Description: The newer version of Django was resulting in the psycopg2.errors.InvalidCursorName as certain functionality has been changed in newer versions. Viewing the documentation and stackoverflow links I realized that this is a known issue while upgrading to the latest version of Django. However, the version of Django we were previously using, 3.2.* the minor version is still compatible with python 3.10.13 so reverted back to that and the error resolved itself.
Technical details: The technical details for the knowledge of other developers. Any detailed caveats or specific deployment steps should be outlined here.
Requirements for PR merge:
Area for explaining above N/A when needed: