Opened 17 years ago
Closed 14 years ago
#5065 closed (wontfix)
Add a post_reset signal to "manage.py reset <app>"
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | post_syncdb post_reset reset management.py | |
| Cc: | mmitar@… | Triage Stage: | Design decision needed |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Currently, there's no equivalent signal to syncdb's post_syncdb for reset. Since reset re-creates a given app's DB elements, it would be useful to be able to perform a subset of the similar types of activities that are done with post_syncdb.
Also, this models the way that all apps are polled for their management.py during syncdb, in case resetting one app has effects on other apps that should be handled via the signal.
Attachments (1)
Change History (5)
by , 17 years ago
| Attachment: | post_reset_signal.patch added |
|---|
comment:1 by , 17 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
comment:4 by , 14 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Wontfix; We're going to deprecate reset/sqlreset because it's fundamentally broken. See #14268
Note:
See TracTickets
for help on using tickets.
Patch that provides post_reset signal against r5788.