Database Design for Custom Fields

 Get my free SQL Cheat Sheets: https://www.databasestar.com/get-sql-cheat-sheets/?utm_sourceviddesc&utm_mediumyoutube&utm_campaign5
 Learn and become confident in SQL: https://databasestar.mykajabi.com/sql-simplified/?utm_sourceviddesc&utm_mediumyoutube&utm_campaign5
The ability to allow custom fields to be added to a database is a common requirement. This could be something the user wants to add when using an application, or for defining reports, or something else.
There are many different ways of allowing custom fields in your database design. There is no one right solution though, as it depends on your requirements, amount of data, and the application.
In this video, I'll share 8 different solutions that can achieve this requirement. Each of them has a sample diagram to help visualise it, and a list of the advantages and disadvantages.
The solutions are (with timestamp links):
1:52 - EAV (Entity Attribute Value)
5:17 - Modified EAV
8:06 - Single Table
10:34 - Class Table Inheritance
12:21 - Concrete Table Inheritance
13:36 - Normalised Tables
15:09 - JSON
16:34 - Dynamic Schema