Changes between Initial Version and Version 2 of Ticket #36774


Ignore:
Timestamp:
Dec 4, 2025, 8:48:41 AM (54 minutes ago)
Author:
Piotr Kubiak
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36774

    • Property Resolution → wontfix
    • Property Status new → closed
    • Property Has patch set

  • Ticket #36774 – Description

    initial v2  
    77The original issue states that Django should "fail gracefully if the connection to the database isn't available." Therefore, I suggest catching the more general `DatabaseError` instead of `OperationalError`, as it covers more cases of database unavailability.
    88
    9 I am happy to prepare a PR.
     9[https://github.com/piotr-kubiak/django/commit/c42edfdbed441afdeba213b502741ef3e8190d85 Proposed fix], I am happy to prepare a PR.
Back to Top