4 ms·
I tried the strict 3NF approach in the past. There weren't performance problems, but there was query ergonomics problems. Combined with "no ORM", the query laye
by ttymck 3y ago
I tried the strict 3NF approach in the past. There weren't performance problems, but there was query ergonomics problems. Combined with "no ORM", the query layer was a labyrinthian minefield.
- hot_gril 3y agoIf you find yourself needing an ORM, probably what you really need is some jsonb. Which maybe strict 3NF goes against, but I would ignore that. Good example is a "user settings" table that you're mostly just going to store and retrieve, such that splitting them into separate cols or tables doesn't help.