Overview of Table Application Management
In SensData Analysis, all access tables (database type tables) and system tables (Events, Users, Items) will be shown in the "Table Application Management". Users need to choose standardized data tables in the Table Application Management to enable the creation of metrics, dimensions, and relationships.
Types/Source of tables
| Table Type | Source |
|---|---|
| Data Table | Third-party data tables integrated or accessed,please refer to the documentation |
| Events Table | Event table, please refer to the documentation |
| Users Table | User table, please refer to the documentation |
| Items Table | Please refer to the documentation |
Introduction to the Functions of the Table Application Management Interface
1. Table Application Management List: Basic information display
2. Data Table Application: Control the visibility of upper-level metrics, dimensions, and relationships.After enabling the data table application, you can create metrics and dimensions using the fields in the data table, and establish relationships using the data table.
3. View: View the fields in the table and the metrics, dimensions, and relationships created using the fields.
When you set a field of a data table as the primary key, it means that the value of this field is unique and non-empty in the table, and it is a unique identifier for each row of data in the table. In addition, the primary key can also ensure the consistency and integrity of the data because it prevents duplicate or invalid data from being inserted into the table.
For example, if you have a table named "Customers," and the "CustomerID" field is able to uniquely identify a row in the table. This primary key ensures that each customer has a unique identifier in the table, making it easier for you to manage and process customer data. The primary key can also be used to establish relationships with data in other tables.
For example, if you have a table named "Orders," you can use the "CustomerID" primary key to associate each order with the corresponding customer. This allows you to easily track the order history of each customer.
- For tables without a primary key, when the user clicks "Set as primary key," the system will verify the "uniqueness and non-emptiness" of the attribute value in the current data.
- If the verification fails, the system will prompt "This column does not meet the uniqueness/non-emptiness condition and cannot be set as the primary key."
- Only one field per table is allowed as the primary key.
- For tables with an existing primary key, when the user clicks "Set as primary key":
- The system will verify if any relationships with a "online" status are using the primary key. If so, it will prompt the user "There are relationships that are using this primary key, and it cannot be taken offline."
- Validate uniqueness/non-empty, show "This column does not meet the uniqueness/non-empty condition and cannot be set as a primary key" if validation fails.