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
New check and domain constraints need to check the existing data. This check can work faster in case of compatible index.
Check constraints generate an SQL, so they already can use indexes, but for other cases this step with select query construction slows down the things compared with direct iteration over TableFilter.
Domain constraints use the TableFilter directly and can't use indexes, but work faster when there are no compatible indexes anyway.
I think they both should use the very similar implementation with direct usage of TableFilter, but they need to create an unmapped clone of the expression, wrap it into ConditionNot and and map columns of TableFilter to it. For domain constraints the VALUE expressions should also be replaced with column expressions on this stage.
The text was updated successfully, but these errors were encountered:
New check and domain constraints need to check the existing data. This check can work faster in case of compatible index.
Check constraints generate an SQL, so they already can use indexes, but for other cases this step with select query construction slows down the things compared with direct iteration over
TableFilter
.Domain constraints use the
TableFilter
directly and can't use indexes, but work faster when there are no compatible indexes anyway.I think they both should use the very similar implementation with direct usage of
TableFilter
, but they need to create an unmapped clone of the expression, wrap it intoConditionNot
and and map columns ofTableFilter
to it. For domain constraints theVALUE
expressions should also be replaced with column expressions on this stage.The text was updated successfully, but these errors were encountered: