id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 1654,Output sql satement on OperationalError,django@…,nobody,"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.",defect,closed,"Database layer (models, ORM)",,normal,fixed,,,Design decision needed,0,0,0,0,0,0