> Well, I have used one and had that assertion. Ease of use means making something that works. For me, it means, under no circumstance, no interleaving of tran

> Well, I have used one and had that assertion. Ease of use means making something that works. For me, it means, under no circumstance, no interleaving of transactions or scheduling of commands, nothing, nichts, nada, can the database be in a state where a business rule is violated. If I need to worry what silly intermediate transaction state can be observed from another transaction, or if I need to worry whether a master record can be deleted without cascade-deleting everything that references it, then the DBMS has failed me. > not normalising when you should or the other way around. I've never seen a situation where anything less than 3NF (actually, ideally, at least EKNF) is acceptable.