Thursday, November 17, 2016
1 change · master
Enhancements to existing features
Database failure logs now include the reason and supporting details, not just the failed query. This helps support and technical teams identify the cause of crashes faster, reducing investigation time and improving issue resolution.
Original PR description
Task: https://www.odoo.com/web#id=27589&view_type=form&model=project.task&action=333&active_id=809&menu_id=4720 Pad: https://pad.odoo.com/p/r.a5fcedd17764c6c9a4d07c763811abaf <dl> <dt>Description of…
Task: https://www.odoo.com/web#id=27589&view_type=form&model=project.task&action=333&active_id=809&menu_id=4720
Pad: https://pad.odoo.com/p/r.a5fcedd17764c6c9a4d07c763811abaf
<dl>
<dt>Description of the issue/feature this PR addresses:</dt>
<dd> Currrently when a query fails execution, it just displays <b>Bad Query:<i>query</i></b>
.<br/>Instead it should say <b>Bad Query:<i>query , query failed because **the reason** </i></b>
</dd>
<dt>Current behavior before PR:</dt>
<dd>Now we say: <em><b>Hey there is an error.</b></em></dd>
<dt>Desired behavior after PR is merged:</dt>
<dd>After this we say: <em><b>Hey there is an error because of **some reason**.</em></dd></dl>
---
```
e.g.
You are creating some object but missing a mandatory field partner_id.
Before:
You can not create this, there is an error.
After:
You can not create this, there is an error.
You are missing a mandatory field **partner_id**
```
> Like everytime here is a video: https://youtu.be/Hz-sbnstr64
## So that we get a clue of what is the reason of the error and how it can be fixed.
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr