Orchid XP v7 wrote:
> 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?

Then use the innodb table type, and be happy.

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

The RDBMS locks things to enforce transactional integrity. I don't do it 
explicitly. I merely start a transaction, and the appropriate rows get 
locked.

Whatever you do to enforce transactional integrity? It takes resources.

-- 
   Darren New / San Diego, CA, USA (PST)
     It's not feature creep if you put it
     at the end and adjust the release date.

Post a reply to this message