The motivation for preventing null values from being passed to SQL was to prevent errors in cases like COLUMN=${Variable}, but your example shows that this is problematic.
We will consider either removing this over validation or allowing the modeler to override it using a special trigger (e.g. <Allow Nulls>) or property.
By the way, if by chance your query condition is built entirely of ANDed comparisons of the type you described (where you're effectively ignoring null values) , the <From> and <To> triggers of Advanced Find may be able to create the SQL for you.
Youval
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign