This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
niota-docs:niota_metadb_conventions [2024/09/13 10:13] admin created |
niota-docs:niota_metadb_conventions [2025/07/17 14:11] (current) |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| === Columns === | === Columns === | ||
| - | Column names in metadatabase tables are build by a internal logic. The first part of the column name carries information about it's logical/business meaning, the second part of the column name tells something about it's specific usage. | + | Column names in metadatabase tables are built by an internal logic. The first part of the column name carries information about it's logical/business meaning, the second part of the column name tells something about it's specific usage. |
| The "business" meaning can for example be: | The "business" meaning can for example be: | ||
| Line 19: | Line 19: | ||
| * description of something | * description of something | ||
| * username of something | * username of something | ||
| + | * sortorder of something | ||
| The specific usage is then fixed be the second part. | The specific usage is then fixed be the second part. | ||
| - | There a column that contains a connection name for logging is build by | + | Therefor a column that contains a connection name for logging is build by |
| - | conn_name ..... the overall info that the content will by a name of a connection | + | **conn_name** ... the overall info that the content will by a name of a connection\\ |
| - | + | + | +\\ |
| - | logging ... for what this connection name will be used. | + | **logging** ... for what this connection name will be used (or log or logged). |
| - | The type of the column must be the same as for the "master domain" for connection name. | + | The type of the column must be the same as for the "master domain" for connection name. The type can be found in the table et_**connection**. |
| result: | result: | ||
| - | * conn_name_logging varchar(16) * | + | **conn_name_logging varchar(16)** |
| it's not logging_connection or logging_conn or something like this. | it's not logging_connection or logging_conn or something like this. | ||
| - | For a timestamp the column name usually has to start with "ts_" followed by the specific usage. | + | For a timestamp the column name usually has to start with **"ts_"** followed by the specific usage.\\ |
| - | For a date the column name usually has to start with "date_" followed by the specific usage. | + | For a date the column name usually has to start with **"date_"** followed by the specific usage.\\ |
| - | ts_log ... timestamp of log entry | + | **ts_log** ... timestamp of log entry\\ |
| - | date_activation .... date of activation | + | **date_activation** .... date of activation\\ |
| other examples | other examples | ||
| - | username .... main domain for username | + | username .... main domain for username\\ |
| - | username_owner ... username for data owner of a table | + | username_owner ... username for data owner of a table\\ |
| - | icon .... main domain for an icon filename | + | **icon** .... main domain for an icon filename\\ |
| - | icon_linked_table column that contains an filename for an icon - used for the linked table in a master/detail link | + | **icon_linked_table** column that contains an filename for an icon - used for the linked table in a master/detail link\\ |
| - | icon_linking_table ..... | + | **icon_linking_table** .... \\ |
| it's not linked_table_icon or linkedicon | it's not linked_table_icon or linkedicon | ||