Opened 17 years ago
Last modified 14 years ago
#5415 closed
Every SQL query should send a signal — at Version 2
| Reported by: | Adrian Holovaty | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Keywords: | feature_request | |
| Cc: | kenneth.arnold@…, Gonzalo Saavedra | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | yes |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Every SQL query should send a signal, using django.core.signals. This will enable all sorts of interesting and useful things, such as logging and debugging functionality.
This should happen at the database backend level, not at the ORM level.
Once this change has been made, django.db.connection.queries should either be removed or refactored to use the signal.
One concern: Are signals fast enough? See #4561.
Change History (2)
comment:1 by , 17 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 17 years ago
| Description: | modified (diff) |
|---|
Note:
See TracTickets
for help on using tickets.