SELECT Statement for Data Queries
You can use a variety of SELECT statements to query for information. The statements can be basic statements or they can be more restrictive to narrow the result set that is returned from the query.
The following example is a basic SELECT statement that is used to query for data.
This statement returns instances of the specified class and any of its subclasses. All of the system and user-defined properties for the classes are included. If a system property is not relevant for a particular query, it contains NULL.
You can use several techniques to reduce the bandwidth required to retrieve the result set, if the execution of the query results in too much overhead and the user is only interested in a subset of the properties. First, queries can replace the asterisk with the desired properties.
The following example shows how to query for specific properties.
The result set includes all system properties and the specified nonsystem properties.
Another technique for narrowing the scope of a query's result set is to use the __CLASS system property. Queries by default return all instances of the specified class and its subclasses. You can use the __CLASS system property to request only instances of the specified class, excluding its subclasses.
The following example shows how to use the __CLASS system property in a WHERE clause.
You can also use the __CLASS system property to restrict the result set to instances of particular subclasses.
The following example shows how to restrict the result set to instances of particular subclasses.
Note If you construct a query with an invalid path for an embedded object, your query does not return an error or any results.
The following example returns an instance of MainClass, assuming that an instance of MainClass exists containing the embedded object EmbedObj with a property P_Uint32 that is equal to "70011".
The following example returns no results and does not return an error, assuming that the embedded object EmbedObj in the instance of MainClass does not have a property INVALID.
Build date: 10/15/2013