This forum allows users to post and respond to "How Do I Do ....." questions. The information contained in this forum has not been validated by K-Rise Systems and, as such, K-Rise Systems cannot guarantee the accuracy of the information.
The not like operator automatically puts the wildcard characters around the value. I set up the where clause like this:
Notlikewhereclause.PNG (24.34 KiB) Viewed 460 times
Notlikewhereclause.PNG (24.34 KiB) Viewed 460 times
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?
Last edited by CathyC on May 3rd, 2023, 11:50 am, edited 1 time in total. word count: 96
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
Notlikewhereclause (2).PNG (29.62 KiB) Viewed 459 times
Notlikewhereclause (2).PNG (29.62 KiB) Viewed 459 times
This is because of how keys worked and the recommended values we gave for Operator.
Operator.png (16.03 KiB) Viewed 451 times
Operator.png (16.03 KiB) Viewed 451 times
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.
Translation