#1174 closed enhancement (invalid)
admin is flaky - it should work even with errors.
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Template system | Version: | 0.90 |
| Severity: | trivial | Keywords: | |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Anytime the database gets corrupted, which appears to be surprisingly easy in django, there's no way to get at delete and modification features in the admin interface as it will generally bomb too. Hence, the only way to fix it is to either wipe the dbase and start all over (acceptable in development phase but obviously a no go in a production environment) or to manually boot up sqlite3 or whatever other direct db access tool applies and craft an SQL statement by hand to delete the corrupted data.
The admin interface should be there specifically FOR such problems. The fact that it bombs out at the first sign of trouble is obviously not good.
Specific cases of db corruption are listed in separate tickets.
Change History (3)
comment:1 by , 19 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 18 years ago
| Component: | Admin interface → Template system |
|---|---|
| milestone: | → Version 1.0 |
| priority: | normal → lowest |
| Severity: | normal → trivial |
| Type: | defect → enhancement |
| Version: | → 0.9 |
Note:
See TracTickets
for help on using tickets.
Please post specific tickets on what database corruption may occur with Django. It's rather problematic to write patches for unspecific problems :-)
It might be useful to discuss some aspects on the django-developer list before posting tickets, though, as it might just be some kind of misunderstanding or misconfiguration (like the charset for the database).