Darren New wrote:

> Honestly, of the 30 or so tables currently in my application, there's 
> about 5 that need transactional consistency.

Well, my application will probably only be about 5 tables, and it's 
simple enough that speed is unlikely to be a problem. So why make things 
more difficult than necessary?

> But where I need it, I turn it on, and take the penalty of speed over 
> correctness.  Enforcing transactions is high overhead if you don't need 
> it. If all your table write-accesses are to a single row, why would you 
> want to lock things?

Why do you need to lock things to enforce transactional integrity? 
Locking is only one (suboptimal) way to solve the problem.

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message