Mimer SQL Engine for liunx 9.3.8

This article describes some of the highlights introduced in Mimer SQL Engine 9. As always, we have a mission to constantly improve performance and to keep up with the latest in database standardization.
Binary and Character Large Objects (BLOBs/CLOBs/NCLOBs)
Mimer SQL Engine 9 has an efficient implementation of the SQL-99 data types BINARY LARGE OBJECT (BLOB) and CHARACTER LARGE OBJECT (CLOB). The data type NATIONAL CHARACTER LARGE OBJECT (NCLOB) was introduced in Mimer SQL 9.2. NCLOB is a data type where Unicode character data can be stored in standardized format, thus enabling a true portability between different platforms (e.g. in a client/server application with a heterogeneous client environment, for example, both Linux and Windows clients). All BLOBs, CLOBs and NCLOBs are stored in the Mimer SQL Engine database and are included in the same transaction control, access control and backup/restore system as more traditional business data.
The maximum size of a BLOB/CLOB/NCLOB is in practice unlimited (the only limitation is the maximum table size in Mimer SQL Engine; 8 TBytes!).
Mimer SQL Engine implements several functions for optimising the performance for insert, select, update, and delete of BLOBs/CLOBs/NCLOBs. When retrieving a BLOB/CLOB/NCLOB over a network, the large object is transferred directly from Mimer SQL Engines communication buffers to the application requesting the BLOB/CLOB/NCLOB without any intermediate temporary storage.
When large objects are accessed from Mimer SQL Engine, the objects are split into packages optimised for best possible performance e.g. over a network. The objects are also accessed asynchronously; the application can read the first packages of the BLOB/CLOB/NCLOB while Mimer SQL Engine delivers the rest of the object.