>>> In February, we start beta on 6.5, which will have multi-version >>> concurrency control, thanks to Vadim. For those of you who did not like >>> our table-level locking, you will be really surprised. Not only do we >>> have row-level locking, we have something even better. In row-level >>> locking, a reader can not read a row that is locked by a writer. In the >>> 6.5 locking system, READERS ARE NEVER BLOCKED, and writers block only if >>> they try to modify a _row_ that another writer has modified and not >>> committed. >>> >>> This is a major feature, better than many commercial databases. There >>> is also no running out of locks like commercial systems, because the >>> transaction ids take care of that. A true NUMERIC type with >>> user-specified precision is also planned for 6.5, thanks to Jan. Bruce, this sounds great.
