Mailing-List: contact dev-help@metamodel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@metamodel.apache.org
From: rposkocil <git@git.apache.org>
To: dev@metamodel.apache.org
Reply-To: dev@metamodel.apache.org
References: <git-pr-139-metamodel@git.apache.org>
In-Reply-To: <git-pr-139-metamodel@git.apache.org>
Subject: [GitHub] metamodel issue #139: Support for NOT / NOT IN operator
Content-Type: text/plain
Message-Id: <20170108211442.75803DFA22@git1-us-west.apache.org>
Date: Sun,  8 Jan 2017 21:14:42 +0000 (UTC)
archived-at: Sun, 08 Jan 2017 21:14:44 -0000

Github user rposkocil commented on the issue:

    https://github.com/apache/metamodel/pull/139
  
    Correct me, please @kaspersorensen, but NegationOperator is much more general than different from and additing another way to propositional logic of filters. Operator Different from is used just for childs of filters and it's represented with <>. For example SQL NOT keyword has a wider usage. You can negate also composed filters on all levels or different from, too. This functionality I didn't found there and thought that it could be fine.
    There is no way to negate IN construct in the currecnt version of MetaModel. That's why Hans created this requirement. There can be IN and NOT IN operators like = and <>. A similiar case.
    So both parts make me sense and don't brake the concept. But I understand that there could be other problems that's why constructors were doubled with negationa and without. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---