Relational Database Design Good Practice: Normalization?
<p>I'm working on an application and its main purpose is to recommend other users based on their preferences and based on their personality (each recommendation is treated separately).
What is consider to be a good practice? To store information in 3 separated tables (<code>users</code>, <code>user_preferences</code> and <code>user_details</code>) or to use a single table <code>users</code> with two <code>jsonb</code> columns?</p>