BOster
Legendary Poster
The global value is just bad all the way around. Some queries you really don't want a dirty read, others really don't matter, having a global setting that decides is just plain bad. And then there is the global timeout setting itself which is ridiculous. Set it too low and all of a sudden every query effectively gets submitted twice increasing database load and reducing performance, set it too high and users may end up waiting twice as long for expensive queries or queries that should only take a micro second now take xx seconds because of record locks.