Changes between Initial Version and Version 2 of Ticket #35394


Ignore:
Timestamp:
Apr 22, 2024, 3:39:03 PM (5 weeks ago)
Author:
Natalia Bidart
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #35394

    • Property Resolution → needsinfo
    • Property Status new → closed
    • Property Summary Warning if 'postgres' database has been rename (e.g. DigitalOcean managed) → Warning if `postgres` database has been rename (e.g. DigitalOcean managed)

  • Ticket #35394 – Description

    initial v2  
    1 This warning is thrown if the 'postgres' database does not exist on the server.  DigitalOcean renames this database to 'defaultdb' which seems to raise this error in dango/db/backends/base/base.py
    2 
     1This warning is thrown if the `postgres` database does not exist on the server.  DigitalOcean renames this database to 'defaultdb' which seems to raise this error in dango/db/backends/postgresql/base.py
    32
    43{{{
    … …  
    1615}}}
    1716
    18 I have searched in the LIBPQ parameters can can't find a setting that allows me to specify this name change as Django seems to have hard-coded the search for the 'postgres' db name or is looking for it in a key called 'service' around line 193 and 218 in base.py.
     17I have searched in the LIBPQ parameters can can't find a setting that allows me to specify this name change as Django seems to have hard-coded the search for the `postgres` db name or is looking for it in a key called 'service' around line 193 and 218 in base.py.
    1918
Back to Top