Monday, April 23, 2018
1 change · master
Resolved issues and error corrections
This fix ensures Odoo checks custom views that do not have a separate technical identifier when the system starts. It helps catch invalid customizations earlier, reducing the risk of view-related issues appearing later during use.
Original PR description
Description of the issue/feature this PR addresses: When Odoo starts up, it validates custom views. Due to an error in the query, custom views without an XML ID are not validated (because `NULL NOT IN (1) IS NOT TRUE` in Postgresql). This is a regression of https://github.com/odoo/odoo/commit/fc91feda3033f which fixed an earlier bug that custom views *with* an XML ID were not validated. Current behavior before PR: Custom views without an entry in ir_model_data are not validated when Odoo starts up. Desired behavior after PR is merged: Custom views without an entry in ir_model_data are not validated when Odoo starts up. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr