Opened 19 years ago
Closed 17 years ago
#1654 closed defect (fixed)
Output sql satement on OperationalError
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | |
| Severity: | normal | 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
Hi,
Is it possible to output the sql statement in the debug information when encountering an OperationalError?
As a default the OperationalError spits out the "there is a problem at xx" with your statement (referring to the sql). While we shouldn't worry about the sql, it can make the error harder to trace because knowing the error from a statement I issued by proxy doesnt necessarily help me. It might help trouble shooting real bugs too.
Change History (2)
comment:1 by , 18 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
comment:2 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Fixed in the queryset-refactor branch.