Difference between revisions of "IDMARKERSCANQUERY"
Line 21: | Line 21: | ||
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. | 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 | + | {{Attention|When selecting the query root node, please consider that possibly a huge amount of derived MetaClasses must be recusively checked for implementing the classification interface! Using a FilterClass that directly implements the interface reduces the processing time to a minimum!}} |
Revision as of 07:41, 3 April 2014
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.