The human-readable table name can be added to the table oemetadata. This name helps to understand the tables context. Currently, this information must be read from the metadata every time a user requests the list of tables within a schema. This is very inefficient. Additionally, this data is relevant for a variety of features in the oep.
Ideas of solution
[ ] Store the readable table name in the table model
(create a nullable field as the name only exists if the user added it to the metadata)
[ ] Handle changes to the table name
(create name, update name/remove name)
Description of the issue
The human-readable table name can be added to the table oemetadata. This name helps to understand the tables context. Currently, this information must be read from the metadata every time a user requests the list of tables within a schema. This is very inefficient. Additionally, this data is relevant for a variety of features in the oep.
Ideas of solution
[ ] Store the readable table name in the table model (create a nullable field as the name only exists if the user added it to the metadata)
[ ] Handle changes to the table name (create name, update name/remove name)
[ ] Handle existing tables
Workflow checklist