Opened 14 years ago
Closed 14 years ago
#12232 closed (duplicate)
Dead links in recent actions and invalid entries in object history
| Reported by: | anonymous | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 1.1 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
If we delete an object the add and change links on recent actions are dead. Also if two objects have the same ID (create a new object after a deletion) they have the same object history.
Attachments (2)
Change History (3)
comment:1 by , 14 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
by , 14 years ago
| Attachment: | t12232_r11366.patch added |
|---|
by , 14 years ago
| Attachment: | t12232_r11366.evolution.py added |
|---|
django-evolution script to add db field for migrations
Note:
See TracTickets
for help on using tickets.
Note the proposed patch changes the LogEntry model -- any such change would require some migration plan, since existing installations do not have this new field in LogEntry and install of a new version of Django wouldn't automatically update existing tables. Thus running the new level of code against a database created with an older level would promptly break.
This is also a duplicate of #1611, which was closed wontfix. (Adrian's first alternative for fixing it is essentially what is proposed here, except he proposed to delete the existing log entries instead of updating them with a flag.) The part that is not a dupe (reusing primary keys of deleted objects) is even more of an edge case.