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 ▶️ https://www.automationhelpers.com/cou...
➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖
Need help with your own No-Code or Automation Project? Reach out to us at 👉 https://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
Watch video Should I Use One or Multiple Tables? No Code Best Practices online, duration hours minute second in high quality that is uploaded to the channel Dan Leeman 16 May 2024. Share the link to the video on social media so that your subscribers and friends will also watch this video. This video clip has been viewed 1,520 times and liked it 45 visitors.
