Many-to-Many relation by default, is that a good strategy?

Question

Defining entities and their relationships at the start of a project is difficult if the requirements keep changing frequently or are not defined (for example, in a startup setup).So, in that case starting with Many-to-Many relationship for entities, and then optimising the relationship as things become clear is a good database design strategy?

mneil · Accepted Answer

https://www.guru99.com/database-normalization.htmlYou usually can get by with 4th normal form but go wild, take it to 11 and it's all you should ever need.

kasey_junk · Answer

You could use blob storage until you know the relationships.You lose a lot of the value of relationships in a schema if you don&rsquo;t know what they are

PaulHoule · Answer

That means adding a lot more tables doesn't it?

Many-to-Many relation by default, is that a good strategy?

https://www.guru99.com/database-normalization.html
You usually can get by with 4th normal form but go wild, take it to 11 and it's all you should ever need.

You could use blob storage until you know the relationships.
You lose a lot of the value of relationships in a schema if you don’t know what they are

That means adding a lot more tables doesn't it?