Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "VIATRA/Query"
< VIATRA
| (58 intermediate revisions by 12 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{VIATRA}} | |
| + | {{caution|Old information|This page is not updated anymore; for more up-to-date details look at the language specification at https://www.eclipse.org/viatra/documentation/ instead.}} | ||
| + | = VIATRA Incremental Query Wiki Documentation = | ||
For the query language, we reuse the concepts of graph patterns (which is a key concept in many graph transformation tools) as a concise and easy way to specify complex structural model queries. High runtime performance is achieved by adapting incremental graph pattern matching techniques based on the Rete algorithm. | For the query language, we reuse the concepts of graph patterns (which is a key concept in many graph transformation tools) as a concise and easy way to specify complex structural model queries. High runtime performance is achieved by adapting incremental graph pattern matching techniques based on the Rete algorithm. | ||
| − | We believe the average programmer using EMF models will like | + | We believe the average programmer using EMF models will like VIATRA Query for the following reasons: |
* declarative queries can be evaluated over EMF without manually traversing the models, | * declarative queries can be evaluated over EMF without manually traversing the models, | ||
| Line 18: | Line 20: | ||
| − | == | + | == VIATRA Query User Documentation == |
| − | * Developing Incremental Model Queries using the | + | * Developing Incremental Model Queries using the VIATRA Query Tooling |
| − | ** [ | + | ** [https://www.eclipse.org/viatra/documentation/tutorial.html Getting started with Query Development] |
| − | + | ** [[VIATRA/Query/UserDocumentation/QueryLanguage|A Short Introduction to the Query Language]] | |
| − | + | ** Advanced topics | |
| − | ** [[ | + | *** [[VIATRA/Query/UserDocumentation/AdvancedPatterns|Advanced pattern language constructs (incl. recursion)]] |
| − | + | *** [[VIATRA/Query/UserDocumentation/SDK/QueryHotspotTesting|Finding query evaluation hotspots]] (since 1.0.0) | |
| − | + | *** [[VIATRA/Query/UserDocumentation/QueryTestFramework|Query Test Framework]] | |
| − | + | *** [[VIATRA/Query/UserDocumentation/DebuggerTooling|VIATRA Query Debugger Tooling]] (since 0.8.0) | |
| − | ** | + | *** [[VIATRA/Query/UserDocumentation/RETE_Visualizer|RETE Visualizer]] |
| − | + | *** [[VIATRA/Query/UserDocumentation/LocalSearch_DebuggerTooling|Local Search Debugger Tooling]] | |
| − | * | + | * Using the VIATRA Query Runtime library |
| − | ** [[ | + | ** [[VIATRA/Query/UserDocumentation/API|API documentation]] |
| − | + | ** [[VIATRA/Query/UserDocumentation/API/LocalSearch|Local Search Support]] | |
| − | * | + | ** [[VIATRA/Query/UserDocumentation/API/BaseIndexer|Base Indexer]] |
| − | ** [[ | + | ** [[VIATRA/Query/UserDocumentation/API/Advanced|Advanced API features]] |
| − | ** [[ | + | ** [[VIATRA/Query/UserDocumentation/API/RunOnce|Run once querying API documentation]] |
| − | + | ** [[VIATRA/Query/UserDocumentation/HeadlessExecution|Headless (standalone) execution of VIATRA queries and unit tests]] | |
| − | ** | + | * Query language extensibility |
| − | * [[ | + | ** [[VIATRA/Query/UserDocumentation/PureWhitelist|Pure whitelist]] (since 1.0.0) for custom code in <code>check()</code> or <code>eval()</code> |
| − | + | ** [[VIATRA/Query/UserDocumentation/CustomAggregators|Custom aggregation operators]] (since 1.4.0) | |
| − | * | + | * [[VIATRA/Query/UserDocumentation/Examples|Examples]] |
| − | ** [[ | + | * [[VIATRA/UserDocumentation/Build|VIATRA Query in CI Environments (Maven artifacts)]] (since 0.8.0) |
| − | + | * [[VIATRA/Query/FAQ|Frequently Asked Questions]] | |
| − | + | ||
| − | + | ||
| − | * | + | |
| − | ** [[ | + | |
| − | * | + | |
| − | ** [[ | + | |
| − | + | ||
| − | ** [[ | + | |
| − | ** [[ | + | |
| − | ** [[ | + | |
| − | ** [[ | + | |
| − | ** [[ | + | |
| − | * | + | |
| − | ** [[ | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | ** [[ | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | * | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 09:38, 30 November 2017
Old information
This page is not updated anymore; for more up-to-date details look at the language specification at https://www.eclipse.org/viatra/documentation/ instead.
This page is not updated anymore; for more up-to-date details look at the language specification at https://www.eclipse.org/viatra/documentation/ instead.
VIATRA Incremental Query Wiki Documentation
For the query language, we reuse the concepts of graph patterns (which is a key concept in many graph transformation tools) as a concise and easy way to specify complex structural model queries. High runtime performance is achieved by adapting incremental graph pattern matching techniques based on the Rete algorithm.
We believe the average programmer using EMF models will like VIATRA Query for the following reasons:
- declarative queries can be evaluated over EMF without manually traversing the models,
- complex interrelated constellations of EMF objects can be easily formulated as a graph pattern,
- the language is expressive and provides powerful features such as negation or counting,
- graph patterns are composable and reusable,
- queries can be evaluated with great freedom, i.e. input and output parameters can be selected at run-time,
- some frequently encountered shortcomings of EMF’s interfaces are addressed:
- easy and efficient enumeration of all instances of a class regardless of location,
- simple backwards navigation along all kinds of references (even without eOpposite)
- finding objects based on attribute value,
- the incremental query evaluation mechanism offers a significant performance boost when frequently querying complex structural patterns with a moderate amount of modifications in-between (e.g. during continuous validation),
- from the declarative representation of queries, pattern matcher code is generated which can be distributed as Eclipse plug-ins with very few dependencies.
VIATRA Query User Documentation
- Developing Incremental Model Queries using the VIATRA Query Tooling
- Using the VIATRA Query Runtime library
- Query language extensibility
- Pure whitelist (since 1.0.0) for custom code in
check()oreval() - Custom aggregation operators (since 1.4.0)
- Pure whitelist (since 1.0.0) for custom code in
- Examples
- VIATRA Query in CI Environments (Maven artifacts) (since 0.8.0)
- Frequently Asked Questions