jimstarkey

3 ms·

1. 1.▲
   by jimstarkey 15y ago

   The system recognizes that two concurrent transactions are trying to update the same record. If the first commits, the second will return an update conflict. The application can then restart the transaction. These are the same MVCC semant
2. 2.▲
   by jimstarkey 15y ago

   The C in ACID is consistent, not serializable (i.e. it's not ASID). Consistency means that declared consistency constraints are enforce -- no dirty writes, no violations of unique indexes, referential integrity, and anything else that the
3. 3.▲
   by jimstarkey 15y ago

   Nope. Not enough info on NuoDB. NuoDB doesn't have a centralized transaction controller. It doesn't have a centralized anything. And it isn't "like" anything else -- all new. It's a distributed database without distributed transactions.
4. 4.▲
   by jimstarkey 15y ago

   The question really isn't SQL but ACID transactions. If you can do ACID transaction, SQL drastically reduces the amount of data transmitted. There is no intrinsic reason that ACID transactions, with or without SQL, can't scale, just that u
5. 5.▲
   by jimstarkey 15y ago

   Marketing statements notwithstanding, the name change was the result of something really boring -- a name conflict with another company. Oh, "New-oh dee bee".