Opened 18 years ago
Closed 18 years ago
#4008 closed (invalid)
Database error misreported(?)
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Template system | Version: | dev |
| Severity: | Keywords: | exception | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Changing values in the database caused a previously-functional page display to fail, exception reported was "Caught an exception while rendering: hour must be in 0..23", no database row or column indicated. However, the values changed were simple integers, not dates or times, and they are not displayed on the page in question.
Stack trace indicates a failure in the database backend, not in the formatting process. It appears that there may be some sort of SQL error, but the original exception message is being supplanted by a format-level exception message.
Change History (2)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Please describe your problem at the django-users mailing list or try the irc channel. Both are pretty good for user support. The ticket system is only for bugs that clearly reside within Django itself.
Couldn't attach sample page display. Unzipped version rejected by spam filter, zipper version caused TRAC error. Sorry.