Should I Use One or Multiple Tables? No Code Best Practices
When should you use a single table vs. multiple tables to represent a similar kind of object like a person, location, event, or thing? In this video, we break down why it's better to try to use a single table (when possible, and describing the same type of object) to reduce complexity and maintenance. We also discuss ways to make this a better experience for our users.
Register for our FREE course on No-Code Architecture ▶️ www.automationhelpers.com/cou...
➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖
Need help with your own No-Code or Automation Project? Reach out to us at 👉 www.automationhelpers.com/con... for a FREE 30 minute consultation!
➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖
00:00 When do we use a single vs. multiple tables in our database?
02:59 Using "types" on a table
03:46 Creating multiple filtered views
04:42 Filtering linked relationships
05:17 Using Airtable interfaces
05:42 Conditional record sections in SmartSuite
07:06 Use case that requires multiple tables for one object type
Пікірлер: 4
Ooof... this video should be a prerequisite to anyone trying to build a database...This 10 min will save HOURS of headaches later :D Great content as usual Dan!
Great overview! Thanks
Thank you sir
Wished I had watched this video before I divided 1 table into 4 tables. I wanted 4 tables, each with some unique fields. I realized the mistake I had made when I tried to update 2 Single Select fields and 1 Mulitple Select field that were common to all 4 tables. To undo my mistake, I had to add extra fields to each of the 4 tables so that they all had the same fields. Then, I imported the records in CSV format from each of the 4 tables into a new single table. Once the new table had all the records, I updated 2 Single Select fields and 1 Mulitple Select field. I created 4 different views with some fields hidden to mimic the 4 discarded tables. Fortunately, Smartsuite made it easy to undo my mistake.