-
Notifications
You must be signed in to change notification settings - Fork 567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get rid of legacy NOT-EQUALS operators from logic expression #338
Comments
teosarca
added a commit
that referenced
this issue
Aug 27, 2016
metas-ts
added a commit
that referenced
this issue
Sep 13, 2016
* FRESH-663 #377 * FRESH-628 #348 * FRESH-622 #338 * FRESH-618 #333 * FRESH-615 #330 * FRESH-613 #327 * FRESH-621 #337 * FRESH-257 * FRESH-369 * FRESH-667 #379 * FRESH-679 #24 * FRESH-671 #21 * FRESH-670 #20 * FRESH-665 #18 * FRESH-657 #16 * FRESH-655 #14 * FRESH-654 #13 * FRESH-651 #11 * FRESH-650 #10 * FRESH-647 #9 * FRESH-646 #7 * FRESH-652 #12
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some legacy logic expressions (see AD_Column.ReadOnlyLogic, MandatoryLogic etc),
we are using the legacy NOT operators: "^", "~".
e.g. @SomeContextVar@~SomeValue
We shall get rid of those and use only "!".
e.g. @SomeContextVar@!SomeValue
Reason: we are about to introduce the XOR logic operator which is using the "~" symbol. That would overlap with the legacy NOT-EQUALS tuple operator.
The text was updated successfully, but these errors were encountered: