Code

Opened 8 years ago

Closed 7 years ago

#1654 closed defect (fixed)

Output sql satement on OperationalError

Reported by: django@… 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: UI/UX:

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.

Attachments (0)

Change History (2)

comment:1 Changed 7 years ago by mir@…

  • Triage Stage changed from Unreviewed to Design decision needed

comment:2 Changed 7 years ago by jacob

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in the queryset-refactor branch.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.