Skip to content
Advertisement

Tag: rdbms

SQL one to one relationship vs. single table

Consider a data structure such as the below where the user has a small number of fixed settings. User UserSettings Is it considered correct to move the user’s settings into a separate table, thereby creating a one-to-one relationship with the users table? Does this offer any real advantage over storing it in the same row as the user (the obvious

How to think in SQL?

How do I stop thinking every query in terms of cursors, procedures and functions and start using SQL as it should be? Do we make the transition to thinking in SQL just by practise or is there any …

Advertisement