Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#13798 closed (fixed)

Add an argument to connection_created signal to distinguish connections in a multi-db environment

Reported by: liangent Owned by: nobody
Component: Database layer (models, ORM) Version: 1.2
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

[10182] introduced connection_created signal. In a single-db environment, using django.db.connection is ok; in a multi-db environment, it's necessary to add an argument to indicate the connection being created. Either a connection name or a connection object is acceptable for me.

Attachments (1)

django-connection-created.diff​ (8.9 KB ) - added by Alex Gaynor 14 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 by Alex Gaynor, 14 years ago

Triage Stage: Unreviewed → Accepted

by Alex Gaynor, 14 years ago

Attachment: django-connection-created.diff​ added

comment:2 by Joshua Ginsberg <jag@…>, 14 years ago

Has patch: set

comment:3 by Rob Hudson, 14 years ago

Patch should add or update the docs for the connection_created signal filed in bug #14054

comment:4 by Russell Keith-Magee, 14 years ago

Resolution: → fixed
Status: new → closed

(In [13672]) Fixed #13798 -- Added connection argument to the connection_created signal. Thanks to liangent for the report, and Alex Gaynor for the patch.

comment:5 by Russell Keith-Magee, 14 years ago

(In [13674]) [1.2.X] Fixed #13798 -- Added connection argument to the connection_created signal. Thanks to liangent for the report, and Alex Gaynor for the patch.

Backport of r13672 from trunk.

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