Difference between revisions of "IDMARKERSCANQUERY"
| Line 9: | Line 9: | ||
}} | }} | ||
== Basics == | == Basics == | ||
| − | In UBIK, id marker scan queries are used for fetching a list of [[Contentclass|ContentClasses]] identified by scan code ([http://dev.metaio.com/sdk/tracking-config/optical-tracking/id-marker/ id marker], [http://en.wikipedia.org/wiki/Barcode barcode], [http://en.wikipedia.org/wiki/QRcode qr code]) from the database. The id marker scan query inherits functionality from [[Query|Query]]. | + | In UBIK, id marker scan queries are used for fetching a list of [[Contentclass|ContentClasses]] identified by scan code ([http://dev.metaio.com/sdk/tracking-config/optical-tracking/id-marker/ id marker], [http://en.wikipedia.org/wiki/Barcode barcode], [http://en.wikipedia.org/wiki/QRcode qr code]) from the database. All of these objects have to fullfill the classification [[SYSCLS_OBJECTWITHIDMARKER]] in order to be found as the query result. The id marker scan query itself inherits functionality from [[Query|Query]] and has the classification interface [[SYSCLS_IDMARKERSCANQUERY]]. |
| − | + | ||
Id marker scan queries can be used in different scenarios with objects identified by scan codes: | Id marker scan queries can be used in different scenarios with objects identified by scan codes: | ||
* data fetching (n records) | * data fetching (n records) | ||
| Line 19: | Line 18: | ||
== Relation between Query and Items == | == Relation between Query and Items == | ||
see [[Query|Query]]. | see [[Query|Query]]. | ||
| − | == | + | ==FilterClass== |
| − | The | + | The FilterCLass is a reference to the root node where all the matching content is beeing compared to the query criteria. The root node itself does not need the classification [[SYSCLS_OBJECTWITHIDMARKER]] as all derived MetaClasses are recursively checked for implementing the classification interface. All the found content then is aggregated to one query result. |
| + | |||
| + | {{Attention|When selecting the query root node, please consider that possibly a huge amount of derived MetaClasses has to be recusively cheched for implementing the classification interface! Using a FilterClass that directly implements the interface reduces the processing time to a minimum!}} | ||
| + | |||
| + | |||
[[Category:System MetaClasses]] | [[Category:System MetaClasses]] | ||
[[Category:Queries]] | [[Category:Queries]] | ||
Revision as of 07:40, 3 April 2014
 IdMarkerScanQuery |
|
|---|---|
| Name | IDMARKERSCANQUERY |
| Namespace | System.IdMarkerScanQuery Custom.IdMarkerScanQuery |
| Internal Name | IdMarkerScanQuery |
| TypeString | {{{typestring}}} |
| RuntimeType | {{{runtimetype}}} |
| Purpose | Configure queries for objects with id markers |
| Version | 2.2.3+ |
Basics
In UBIK, id marker scan queries are used for fetching a list of ContentClasses identified by scan code (id marker, barcode, qr code) from the database. All of these objects have to fullfill the classification SYSCLS OBJECTWITHIDMARKER in order to be found as the query result. The id marker scan query itself inherits functionality from Query and has the classification interface SYSCLS IDMARKERSCANQUERY. Id marker scan queries can be used in different scenarios with objects identified by scan codes:
- data fetching (n records)
- finding a single or a set of recordset(s)
- used as definition of root nodes in a View
Query, QueryItem
see Query.
Relation between Query and Items
see Query.
FilterClass
The FilterCLass is a reference to the root node where all the matching content is beeing compared to the query criteria. The root node itself does not need the classification SYSCLS OBJECTWITHIDMARKER as all derived MetaClasses are recursively checked for implementing the classification interface. All the found content then is aggregated to one query result.
 | When selecting the query root node, please consider that possibly a huge amount of derived MetaClasses has to be recusively cheched for implementing the classification interface! Using a FilterClass that directly implements the interface reduces the processing time to a minimum! |
