DataModel is one kind of Model (the other kinds are ThingModels and AppModels). Therefore it has all the properties of Models (Lifecycle of models, Model Attributes, Unique and Constraints).
A DataModel is defined with a Name and any number of Model Attributes. DataModels do not have Actions.
Example of a DataModel:
A DataModel definition with three simple a\Attributes:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
#
DataModel(Name="VendorInfo"):
Sid(name: "VendorSysId")
String(name: "vendorName")
String(name: "vendorTitle") |
DataModel is often used in TQL applications to represent logical entities (versus physical things that have direct interactions with the application). For example, a user, a vendor, or a ladder.
The purpose of DataModel is to store just enough data that may be required to complete IoT Application logic. DataModels are not meant for general purpose large volume of transnational data.
DataModel can be created, read, update and deleted using TQL queries.
| Expand | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
|