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
Problem: in READ UNCOMMITTED isolation, a SELECT reading an indexed
generated column could trigger an assertion failure in debug binaries.
my_eval_gcolumn_expr*() is called by the storage engine, which may request to
evaluate more generated columns than read_set/write_set says.
For example, InnoDB's row_sel_sec_rec_is_for_clust_rec() reads the full
record from the clustered index and asks us to compute generated columns
that match key fields in the used secondary index. So we trust that the
engine has filled all base columns necessary to requested computations,
and we ignore read_set/write_set.
The in_purge branch becomes unneeded.
I noticed that the my_rec argument of innobase_get_computed_value()
is always NULL, so in agreement with Jimmy I remove it.
0 commit comments