Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Master sale computes vfe #42709
Until now, stored compute fields were computed after database insertion. This meant that required fields or constraints couldn't be used on computed fields, unless a default was specified. But using a default meant that the field wasn't computed after insertion either, because it was protected against recomputation. We sometimes do want to explicitly compute some computed stored fields AFTER INSERT, mainly: * statistics fields computed with search/read_group/... * fields potentially referencing the current record (e.g. res.partner.commercial_partner_id) * field referencing the first one of a m2m/o2m relational field (only if stored) * fields depending on the create_date/write_date/create_uid/write_uid ... Those fields can be specified as pre_compute=False to force their computation post record creation.
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments.