Data modelling, in the context of Baserow, is the process of determining the appropriate tables and fields to create in your database to accurately represent your data.
Incorrect data modelling can result in duplicate entries, leading to unnecessary work and potential errors if updates are missed. It can also lead to empty cells, reducing the usability and visibility of your data.
Getting your initial data structure right is crucial. Migrating to a new structure after adding many rows is difficult and time-consuming, so it’s best to get it right from the start.
When modelling data in Baserow, you can generally follow the best practices for conventional relational databases. Since Baserow is a no-code database, general database best practices apply.
Suppose you’re storing employee data in a Baserow database, including workplace departments and clients. The current table looks like this:
Employees table
The “Clients” and “Department Address” columns contain multiple pieces of information in a single cell. To improve this, we should create separate tables for departments and clients.
Departments table
Having a separate table for departments allows us to define the address once and easily update it if needed.
Clients table
Creating a separate table for clients enables us to add additional information and make changes that automatically apply to the entire database.
Employee table
The employee table now links to the “Clients” and “Departments” tables.
Employee table
If you need additional information, such as the city of the department, you can add a lookup field to retrieve that data.
To learn more about Baserow and everything you can do with the platform, sign up for free!
What’s your story? Tell us how you use Baserow