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
The problem is that we lose a non-deterministic property of a UDF
function when that function is part of a derived table that is merged
into the outer query block (or is part of a subquery that is converted
to a semi-join). It happens because the function fix_after_pullout()
forgets about this property. The function update_used_tables() handles
the property by adding some special logic that checks the
non-deterministic property before updating used tables information.
The fix is to add a member m_non_deterministic that is set to true
during resolving and used in fix_after_pullout() and
update_used_tables() to set correct values for used_tables().
The member is used by get_initial_pseudo_tables() and means that we can
also remove the special update_used_tables() implementation.
Change-Id: I26ea348e450acb92062df5b676e2a24110af5dd8
0 commit comments