With #1946 the use of update_row() is expected to increase quite a bit. The results of this method are not currently cached along with study tables. That would mean this may result in performance decreases, especially for larger tables.
I'll have to figure out a way to nicely cache both the original values and the updated values. Brute force solution is of course to store 2 versions of the table, but I'd rather do it cleaner if feasible..
With #1946 the use of
update_row()is expected to increase quite a bit. The results of this method are not currently cached along with study tables. That would mean this may result in performance decreases, especially for larger tables.I'll have to figure out a way to nicely cache both the original values and the updated values. Brute force solution is of course to store 2 versions of the table, but I'd rather do it cleaner if feasible..