Opened 5 years ago

Closed 3 years ago

#30934 closed New feature (fixed)

django.db.backends logging output should include the database alias

Reported by: David Winterbottom Owned by: Nick Pope
Component: Database layer (models, ORM) Version: dev
Severity: Normal Keywords: logging
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by David Winterbottom)

As this is essential information when working with database routing.

PR: ​https://github.com/django/django/pull/11994

Change History (8)

comment:1 by David Winterbottom, 5 years ago

Description: modified (diff)

comment:2 by Nick Pope, 5 years ago

Has patch: set
Triage Stage: Unreviewed → Accepted
Version: 2.2 → master

​PR

This sounds perfectly reasonable to me and is a trivial change.

comment:3 by Carlos_Mir_de_Souza, 5 years ago

Triage Stage: Accepted → Ready for checkin

comment:4 by Mariusz Felisiak, 5 years ago

Triage Stage: Ready for checkin → Accepted

CarlosMirdeSouza, please check ​patch-review-checklist before you will mark a ticked as "Ready for checkin", few changes are missing e.g. versionchanged admonitions.

comment:6 by Mariusz Felisiak, 5 years ago

Needs documentation: set
Owner: changed from nobody to David Winterbottom
Patch needs improvement: set
Status: new → assigned

comment:7 by Nick Pope, 3 years ago

Needs documentation: unset
Owner: changed from David Winterbottom to Nick Pope
Patch needs improvement: unset

New ​PR.

comment:8 by GitHub <noreply@…>, 3 years ago

Resolution: → fixed
Status: assigned → closed

In fa35c8bd:

Fixed #30934 -- Included database alias in django.db.backends log messages.

This is useful when working with database routing as you want to know
where each query is being executed.

Co-authored-by: David Winterbottom <david.winterbottom@…>

Note: See TracTickets for help on using tickets.
Back to Top