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!
➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖
👉 Sign Up Now: https://a2m8.help/yt-subscribe
➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖
Timestamps:
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
On this page of the site you can watch the video online Should I Use One or Multiple Tables? No Code Best Practices with a duration of hours minute second in good quality, which was uploaded by the user Automation Helpers 16 May 2024, share the link with friends and acquaintances, this video has already been watched 2,323 times on youtube and it was liked by 52 viewers. Enjoy your viewing!
