GitHub user kaspersorensen opened a pull request:
https://github.com/apache/metamodel/pull/146
METAMODEL-63: UnionDataSet
Here's my attempt at designing/solving METAMODEL-63.
Ideally we would support UNION also as part of our Query language. But that
seems like a huge change and a much more low-hanging fruit would be to allow
unions via a special `DataSet` implementation.
I also introduced a new interface, `InvokableQuery`. I've often had the
need to pass around both DataContext and Query (because those two are needed in
combination to produce the `DataSet`). The new interface allows passing these
around in a more coherent and encapsulated way.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kaspersorensen/metamodel METAMODEL-63-union
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metamodel/pull/146.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #146
----
commit fe80412708e0bcd5e244e9e8f8b0d17ef05fcab4
Author: Kasper Sørensen <[email protected]>
Date: 2017-06-08T04:12:27Z
METAMODEL-63: Added UnionDataSet
commit 78d85d6d322590adf66b37c75c28f43703f73933
Author: Kasper Sørensen <[email protected]>
Date: 2017-06-08T04:39:27Z
METAMODEL-63: Slight redesign to introduce building block InvokableQuery
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
