|
|
|
Easier handling of large SQL fields has been a common request. XML and other large text objects are frequently larger than 8192 bytes requiring LONG field handling. LONG fields can be up to 2GB and are handled quite differently than standard CHAR or VARCHAR fields as a handle to data is required. Data is then streamed from the field through the handle with calls such as GetBytes(). Further, LONG fields were not supported in stored procedure interfaces requiring extensive workarounds to handle large character fields.
The maximum size of a field in SQL has been increased from 8,192 to 65,500 characters. This extends the useful size for character-based data and is much easier to handle directly in SQL.
BINARY, VARBINARY, CHAR, and VARCHAR types have been expanded to a maximum size of 65,500 bytes, which means it is not necessary to use LVARBINARY or LVARCHAR for lengths between 8182 and 65500.
In addition, stored procedures have been extended such that LONG fields can be accessed within them. However, it remains not possible to pass a LONG field into a stored procedure argument.
At the c-treeDB level, the "scale" and "precision" properties have been adjusted to be consistent with the information in the system tables.
