#30934: django.db.backends logging output should include the database alias
-------------------------------------+-------------------------------------
Reporter: David Winterbottom | Owner: Nick Pope
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: logging | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"fa35c8bdbc6aca65d94d6280fa463d5bc7baa5c0" fa35c8bd]:
{{{
#!CommitTicketReference repository=""
revision="fa35c8bdbc6aca65d94d6280fa463d5bc7baa5c0"
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.winterbot...@gmail.com>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30934#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.d7393f07e0d5d01cc91a2c4c3c3ab984%40djangoproject.com.
