Changes between Version 1 and Version 2 of Ticket #34454


Ignore:
Timestamp:
Apr 3, 2023, 9:02:06 AM (20 months ago)
Author:
Tim Graham
Comment:

I don't think you've provided enough details to make this ticket actionable. I guess you will need to debug the issue further or at least provide a minimal sample project that reproduces the problem. I guess the issue doesn't occur with pyscopg2?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #34454

    • Property Resolutionneedsinfo
    • Property Status newclosed
  • Ticket #34454 – Description

    v1 v2  
    55The error seems to occur randomly, and I am not sure what is causing it. I have double-checked that the username and password specified in the DATABASES setting in my Django project are correct and have the necessary permissions to access the database.
    66
    7 I am using psycopg3 version 3.1.8 and PostgreSQL version 4.2rc1.
     7I am using psycopg3 version 3.1.8 and Django version 4.2rc1.
    88
    99///This error can occur randomly, and sometimes it can be correctly linked to the database
Back to Top