Hacker News new | ask | show | jobs
by frollogaston 49 days ago
If you find yourself doing a lot of explicit transactions, it can be a sign that your schema isn't as normalized as it should be.
1 comments

How does better normalization reduce the need for explicit transactions?
The need to change two separate tables atomically means that you probably have info duplicated. Also it can be non-ideal in a web backend cause it means keeping DB connections open longer.
Sorry ignore the second sentence, I meant keeps the connection checked out of the pool longer, but also it has nothing to do with normalization.