Having even two tables is bad as joins enter the picture. It is why I strongly prefer services that can make do with a single table even if there exists significant redundancy among its values.
Imagine for example a dating app. Do you really need more than one table? I am not sure you do. Some columns can use array datatypes and other nesting, and joins are never needed for them except to the associated profile. Granted, updates can become a bit complicated, but that's okay.
1 comment
[ 3.0 ms ] story [ 12.6 ms ] threadImagine for example a dating app. Do you really need more than one table? I am not sure you do. Some columns can use array datatypes and other nesting, and joins are never needed for them except to the associated profile. Granted, updates can become a bit complicated, but that's okay.