New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FIX] models: using unknown fields makes CRUD methods crash #37094
Conversation
d1004cc
to
69a2a8b
Compare
127a397
to
78c871d
Compare
The basic ORM methods should not silently discard unknown fields, as they may be a sign of broken code.
78c871d
to
4bcb6c1
Compare
@@ -100,7 +99,6 @@ def _check_holidays_status(holiday_status, ml, lt, rl, vrl): | |||
HolidayStatusManagerGroup.create({ | |||
'name': 'WithMeetingType', | |||
'allocation_type': 'no', | |||
'categ_id': self.env['calendar.event.type'].with_user(self.user_hrmanager_id).create({'name': 'NotLimitedMeetingType'}).id, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, this will make the behavior uniform for all cases, and definitely catch mistakes and typos earlier. Not much of a semantic change for 13.0 either, as the refactored ORM already blocked read()
on non-existant fields.
@robodoo rebase-ff r+
Merge method set to rebase and fast-forward |
Merged at 9492b01, thanks! |
The basic ORM methods should not silently discard unknown fields, as
they may be a sign of broken code.