Features:
DEX 4.6 makes DEX aCiD.
- Durability: Changes will persist thanks to the complete Recovery Manager. The recovery manager keeps your DEX databases automatically backedup all the time, and provides recovery tools in case you may need to delete unfinished Tx.
- Consistency: After each Tx the GBD is consistent, guaranteed with the operations order.
- Atomicity: Better autocommitted transactions (not rollback yet).
- Isolation: Simple isolated Tx with S/X blocking.
(From the release page.)
Useful links:
Documentation, including a new “Getting Started.”
Using TEXT attribute (NEW 4.6 interface!) – Java
I appreciated the “Getting Started” document offering the example application in Java, C# and C++.
On the other hand, it is a bit “lite” in terms of examples.
So I looked at the Technical Documentation because it was described as:
Complete technical documentation of the API, with examples of use, in pdf and html formats.
So, searching on the term “example” (in the pdf JavaDoc documentation for DEX 4.6) I find:
- com.sparsity.dex.gdb.Condition – regex examples
- com.sparsity.dex.gdb.Objects – “example”
- com.sparsity.dex.gdb.Session – “example” While I am here, correction: “Objects or Values instances or even session attributes are an example of temporary data.” -> Objects, values instances, and session attributes are examples of temporary data.
- com.sparsity.dex.io.CSVReader – “example”
- com.sparsity.dex.script.ScriptParser – one line examples from pp. 268-270
Having said all that, the documentation isn’t a reason to avoid DEX.
I am going to throw a copy on my Ubuntu box before the end of the month.