Query language - Revision history

Olli: /* Aggregate */

2014-09-23T08:12:58Z

‎Aggregate

Olli: /* Notes, known issues, and limitations */

2014-04-07T10:56:17Z

‎Notes, known issues, and limitations

Olli: /* Introduction */

2013-11-29T15:02:48Z

‎Introduction

Olli: /* Topic maps directives */

2013-11-29T13:47:53Z

‎Topic maps directives

Olli: /* Topic maps directives */

2013-11-29T13:46:20Z

‎Topic maps directives

Olli: /* Topic maps directives */

2013-11-29T13:45:47Z

‎Topic maps directives

Olli: /* Topic maps directives */

2013-11-29T13:42:34Z

‎Topic maps directives

Olli: /* Notes, known issues, and limitations */

2013-11-29T13:40:29Z

‎Notes, known issues, and limitations

Olli: /* Directives */

2013-11-29T13:39:04Z

‎Directives

Olli: /* Introduction */

2013-11-29T13:24:52Z

‎Introduction

← Older revision		Revision as of 08:12, 23 September 2014
Line 229:		Line 229:

	* [[Count (query directive) \|Count]](Directive directive) - Counts the number of rows returned by the inner directive using same input the ''Count'' directive got.		* [[Count (query directive) \|Count]](Directive directive) - Counts the number of rows returned by the inner directive using same input the ''Count'' directive got.
		+
		+	* [[Concat (query directive) \|Concat]](Directive directive) - Concatenates the String representation of active column values.

	* [[Sum (query directive) \|Sum]](Directive directive) - Returns the sum of values of active column.		* [[Sum (query directive) \|Sum]](Directive directive) - Returns the sum of values of active column.

← Older revision		Revision as of 10:56, 7 April 2014
Line 307:		Line 307:
	Instances().as("#instance")		Instances().as("#instance")
	)		)
		+
		+
		+	== See also ==
		+
		+	Wandora also supports [[TMQL]] queries.

@@ Line 177: / Line 177: @@
 Some directives take ''TopicOperand''s as parameters. These are essentially things that will resolve into a topic in some way. It can be an actual Topic object, a String containing the subject identifier of a topic or a directive which produces the topic as the default value of the first result row. If the directive operand produces more than one row, all the other rows are ignored. The operand gets as input the same input row as the directive using the operand.
-The most usual case is to use the subject identifier, you'll pass this to the directive simply as a String. Only when the operand somehow depends on the input row, do you need to use a directive as an operand. And in this case you typically just have an ''Of'' directive which picks one column from the input row but in theory the directive could be as complex as you want.
+The most usual case is to use the subject identifier, you'll pass this to the directive simply as a String. The following example illustrates this. A topic is passed directly to ''IsOfType'' as a subject identifier String. So this gets all instances that are of the specified type.
 You can find examples of queries on all of the directive pages (see list below). There are also some more [[Complex example queries]] on a separate page.

@@ Line 259: / Line 259: @@
 * [[IsOfType (query directive) |IsOfType]](TopicOperand op) - Includes rows where the active column value is an instance of the specified type.
-* [[Occurrence (query directive |Occurrence]]([TopicOperand type [,TopicOperand version] ]) - Gets the occurrence with specified type and version from the active column value of input. You can leave out the version to get all occurrences of a type or both parameters to get all occurrences in the topic.
+* [[Occurrence (query directive |Occurrence]]([TopicOperand type][,TopicOperand version]) - Gets the occurrence with specified type and version from the active column value of input. You can leave out the version to get all occurrences of a type or both parameters to get all occurrences in the topic.
 * [[Players (query directive) |Players]](TopicOperand associationType,TopicOperand r1[,...]) - Gets players of specified roles from associations of specified type.
@@ Line 269: / Line 269: @@
 * [[Types (query directive) |Types]]() - Gets all types of the active column value of input.
-* [[Variant (query directive) |Variant]]([TopicOperand type [,TopicOperand version] ]) - Gets the variant name with the specified type and version from the active column value of input. You can leave out the version to get all variants of a type or both parameters to get all variants in the topic.
+* [[Variant (query directive) |Variant]]([TopicOperand type][,TopicOperand version]) - Gets the variant name with the specified type and version from the active column value of input. You can leave out the version to get all variants of a type or both parameters to get all variants in the topic.
 * [[Variant2 (query directive) |Variant2]](TopicOperand scope, [...]) - Gets the variant name with the specified scope. You can use this to get variants with any kind of scope while the other directive is specifically for variants which have exactly two topics in the scope, a type and a version.

@@ Line 271: / Line 271: @@
 * [[Variant (query directive) |Variant]]([TopicOperand type [,TopicOperand version] ]) - Gets the variant name with the specified type and version from the active column value of input. You can leave out the version to get all variants of a type or both parameters to get all variants in the topic.
-* [[Variant2 (query directive) |Variant2]]([TopicOperand scope, [...]) - Gets the variant name with the specified scope. You can use this to get variants with any kind of scope while the other directive is specifically for variants which have exactly two topics in the scope, a type and a version.
+* [[Variant2 (query directive) |Variant2]](TopicOperand scope, [...]) - Gets the variant name with the specified scope. You can use this to get variants with any kind of scope while the other directive is specifically for variants which have exactly two topics in the scope, a type and a version.
 === Others ===

← Older revision		Revision as of 13:42, 29 November 2013
Line 270:		Line 270:

	* [[Variant (query directive) \|Variant]]([TopicOperand type [,TopicOperand version] ]) - Gets the variant name with the specified type and version from the active column value of input. You can leave out the version to get all variants of a type or both parameters to get all variants in the topic.		* [[Variant (query directive) \|Variant]]([TopicOperand type [,TopicOperand version] ]) - Gets the variant name with the specified type and version from the active column value of input. You can leave out the version to get all variants of a type or both parameters to get all variants in the topic.
		+
		+	* [[Variant2 (query directive) \|Variant]]([TopicOperand scope, [...]) - Gets the variant name with the specified scope. You can use this to get variants with any kind of scope while the other directive is specifically for variants which have exactly two topics in the scope, a type and a version.

	=== Others ===		=== Others ===

@@ Line 281: / Line 281: @@
 Most of these things you can work around by using the [[Eval (query directive) |Eval]] directive. It takes a custom script which can then do pretty much anything. See examples in the directive page.
 * Explicit '''new''' operator in front of directives can be omitted.
-* You can use the query language with [http://www.jython.org Jython] scripts too. You need version 2.5.1 of Jython or later. Jython scripts don't return the value of the last line, instead you have to assign the query directive in a variable ''query''. The syntax is naturally slightly different, especially you don't use the ''new'' operator when constructing new classes and there are the usual python restrictions to whitespace use. Also note that the ''Eval'' directive still uses the default scripting engine i.e. ECMAScript, even if invoked through Jython. For example one of the introduction examples in Jython:
+* You can use the query language with [http://www.jython.org Jython] scripts too. You need version 2.5.1 of Jython or later. Jython scripts don't return the value of the last line, instead you have to assign the query directive in a variable ''query''. The syntax is naturally slightly different, specifically you don't use the ''new'' operator when constructing new classes and there are the usual python restrictions to whitespace use. Also note that the ''Eval'' directive still uses the default scripting engine i.e. ECMAScript, even if invoked through Jython. For example one of the introduction examples in Jython:
   from org.wandora.query2 import *

@@ Line 239: / Line 239: @@
 * [[Exists (query directive) |Exists]](Directive directive) - Includes rows where the inner directive returns a non-empty result using the row itself as input.
-* [[IsOfType (query directive) |IsOfType]](String si) - Includes rows where the active column value is an instance of the specified type.
+* [[IsOfType (query directive) |IsOfType]](TopicOperand op) - Includes rows where the active column value is an instance of the specified type.
 * [[Not (query directive) |Not]](WhereDirective directive) - Returns rows which do not satisfy the inner filtering directive.
@@ Line 257: / Line 257: @@
 * [[Instances (query directive) |Instances]]() - Gets all instances of the active column value of input.
-* [[IsOfType (query directive) |IsOfType]](String si) - Includes rows where the active column value is an instance of the specified type.
+* [[IsOfType (query directive) |IsOfType]](TopicOperand op) - Includes rows where the active column value is an instance of the specified type.
-* [[Occurrence (query directive |Occurrence]](String type,String version) - Gets the occurrence with specified type and version from the active column value of input.
+* [[Occurrence (query directive |Occurrence]]([TopicOperand type [,TopicOperand version] ]) - Gets the occurrence with specified type and version from the active column value of input. You can leave out the version to get all occurrences of a type or both parameters to get all occurrences in the topic.
-* [[Players (query directive) |Players]](String associationType,String r1[,...]) - Gets players of specified roles from associations of specified type.
+* [[Players (query directive) |Players]](TopicOperand associationType,TopicOperand r1[,...]) - Gets players of specified roles from associations of specified type.
 * [[SubjectIdentifiers (query directive) |SubjectIdentifiers]]() - Gets all subject identifiers of the active column value of input.
@@ Line 269: / Line 269: @@
 * [[Types (query directive) |Types]]() - Gets all types of the active column value of input.
-* [[Variant (query directive) |Variant]](String type,String version) - Gets the variant name with the specified type and version from the active column value of input.
+* [[Variant (query directive) |Variant]]([TopicOperand type [,TopicOperand version] ]) - Gets the variant name with the specified type and version from the active column value of input. You can leave out the version to get all variants of a type or both parameters to get all variants in the topic.
 === Others ===

@@ Line 174: / Line 174: @@
   | align="center" | 9
   |}
 You can find examples of queries on all of the directive pages (see list below). There are also some more [[Complex example queries]] on a separate page.