You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In theory we know all local fields, that are needed to update a cf, thus could lower the db/ORM/memory stress by only loading those fields with .only.
Needs some investigation, whether the savings are worth the trouble, because there is a nasty downside - if a local field was forgotten in the self-depends rule, the field value gets loaded lazy for every single object, thus runtime might explode again for bigger changesets.
The text was updated successfully, but these errors were encountered:
This is also linked to the issue, that we currently dont have any measures in place to enforce dependency strictness between depends and the function. Also see #135 (comment).
In theory we know all local fields, that are needed to update a cf, thus could lower the db/ORM/memory stress by only loading those fields with
.only
.Needs some investigation, whether the savings are worth the trouble, because there is a nasty downside - if a local field was forgotten in the self-depends rule, the field value gets loaded lazy for every single object, thus runtime might explode again for bigger changesets.
The text was updated successfully, but these errors were encountered: