K-Rise Systems

The not like operator automatically puts the wildcard characters around the value. I set up the where clause like this: And expected:
select * from EC_Order_Header WHERE OrderNumber not like 'ORH%'
since the single quotes would be auto filled by the value being an ansistring
but this way I get to choose where the wildcard character goes

but this is what ran:
select * from EC_Order_Header WHERE OrderNumber not like '%ORH%%'

is this what its supposed to do?

If I click the where clause at a higher level, it shows it as I expected and without the wildcard characters, so I think automatically adding them should not be done. Or in the preview show them

This is because of how keys worked and the recommended values we gave for Operator. We would then change the value based on the operator
like/not like: %{value}%
likeleft: {value}%
likeright: {value}%
likeexact: {value}

Our thoughts are to drop likeleft, likeright, likeexact and do not modify the value for like/not like so you would have to add the % yourself. We would create a dbchange that would go and update all existing values to be %{value}% so they would continue to work as is.

Task 10182 has been created for this.

This change has been implemented as of DesignTime Revision 2395, RunTime Revision 1059, and ECC Revision 120.