Skip to content

expressions `0=1` and `1=1` now bypass complex expression check for external UBLQ

Pavel Mashliakovskiy requested to merge feature/simpleFalsyExpression into master

expressions 0=1 and 1=1 now bypass complex expression check for external UBLQ. This allows to send from client whereItem {expression: '0=1', condition: 'custom'}. Such expressions are used by Repository to replace always positive and always negative where items by 1=1 and 0=1.

Before this feature Repository replace such where item by {expression: '0', condition: '=', value: 1} and DB server builds non-optimal query execution plane, because on prepare stage parameter value 1 is unknown.

Example of always negative expression: {expression: 'attrName', 'condition: 'in', value: []}

Edited by Pavel Mashliakovskiy

Merge request reports