Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
We have optimization in ExpressionFactory for (not)inExp() methods for the empty values that returns just ASTFalse or ASTTrue
But when we create ASTIn manually we don't have this optimization and that results in incorrect SQL like t0.ARTIST_NAME IN ().
We could optimize that on our end, and that would benefit users who work directly with raw AST tree.