Output sql satement on OperationalError
|Reported by:||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:|
|Cc:||Triage Stage:||Design decision needed|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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.