FWD » Core Development » Database

Options:

• LOB-AREA
• LOB-BYTES
• LOB-SIZE
• CLOB-CODEPAGE
• CLOB-COLLATION
• CLOB-TYPE

Eric, these are from the .df, right?

Ovidiu: can you take a quick look at would need to be implemented?

First, a disclaimer: there is little information about these attributes, including on progress.com. The statements below represent MY current understanding of these attributes and might not represent the truth. Please let me know if you think that I am wrong and will correct them.

• LOB-AREA - I do not think we have an equivalent idiom in FWD for this. The storage in SQL is transparent for us. Nothing to do here, even saving this to .p2o or DMO annotation might be useless.
• LOB-BYTES and LOB-SIZE - in all places I found the same value, but expressed in different units: the former in bytes, the latter in binary multipliers, with incorrect ISO prefix. For example: LOB-BYTES 104857600 | LOB-SIZE 100M. I think this is also of less importance. All we can do is a validation at runtime and raise a specific error, if the case. A more important idea is to collect these during conversion and provide a statistic at the end so that the admin will be able to configure the database. Some dialects allows LOB of specific sizes. Limiting the LOB size (to just right size for such column) may allow SQL engines to do some optimisations;
• CLOB-CODEPAGE and CLOB-COLLATION - these are important and the first is, at least partially, supported. Note that currently, the DBCODEPAGE and DBCOLLATION functions are implemented and they return the values from the SQL database. I am assuming these attributes will also have to be part of the schema. If not present the default attributes from database will be used;
• CLOB-TYPE - my research did not find any useful information on this attribute. Must be something about how it is stored, maybe historical versioning. The only values I found for it are 1 and 2.