AUL version 4 will support LOB data type, including inline LOB, in row LOB and out of row LOB. I need to introduce few new options of AUL, the following two are only related to CLOB data type:
1, SET CLOB_EDIAN {BIG | LITTLE}
If you use fixed length character set in your database (single byte character or those name suffixed with FIXED), the content in CLOB is stored in the same character set with your database's character set. If you use var-length character set in you database, the content in CLOB is stored in unicode format. One unicode char consists of two bytes, so there is byte edian problem, in 9i or previous release, the byte edian of CLOB keeps the same with CPU, in 10g or above, it's always using big edian. This option is used to specify the CLOB byte edian, default is little edian.
2,SET LOB_CONVERT {0:NONE | 1:GBK | 2:UTF8}
According to previous description of CLOB, the value maybe stored in unicode format, it will bring some troubles to us when recovery, so I design a feature to convert them from unicode to GBK or UTF8 format. This option have three option: 0, do no conversion, 1, convert to GBK encode, 2 convert to UTF8 encode. I haven't write out the code of other character set conversion.
The third option is to decide where the LOB content to be recovered for both CLOB and BLOB.
3,SET LOB_STORAGE {0:INLINE | 1:FILE | 2:NONE}
AUL 4 still support two recover format: text and dmp. When recover to text format, lob value can be stored with other columns in the same file (value 0), or store in seperate file (value 1), only the file name is stored with other columns. If you specify the value 2, AUL will not recover LOB data, treat it as a NULL. The default value is 0, store in the same file with other columns.
NCLOB is not supported, and no plan to support it.