News for hackers. Stuff that matters.
Re:Ask HN: Dirty Reads for Databases: Good Thing or Bad? by Robin_Message on Thursday March 29, 2018 @06:25AM (#16705892)
Since the transaction that did the write is uncommitted, dirty reads are generally a bad idea as you may act based on something that is subsequently thrown away.

Only useful use I've found for them: emulating sequences on a DB without them.

Re:Ask HN: Dirty Reads for Databases: Good Thing or Bad? by jonballant on Thursday March 29, 2018 @08:02AM (#16706267)
Could another use be to debug something that is happening inside a transaction?

https://stackoverflow.com/questions/2471055/why-use-a-read-u...

Re:Ask HN: Dirty Reads for Databases: Good Thing or Bad? by jonballant on Thursday March 29, 2018 @07:46AM (#16706191)
This is a good article that outlines some of the pros of the Read Uncommitted Level. When speed is pertinent and you need to run multiple transactions quickly, such as an E-commerce store, Read Uncommitted allows you to immediately execute the next transaction, without waiting for the first to complete execution.

http://codingsight.com/understanding-dirty-read-problem-sql-...