We're currently still using SDAC 3.55 and haven't upgraded because it's adequate for our needs. Looking at the change history, it mentions the following for version 3.70
3.70.1.27 12.05.06
- Bug with using alternative memory managers fixed
We're using FastMM in our application. Could you pls elaborate on what the bug is, so we can decide if we need to upgrade?
Thanks.
SDAC 3.55
There was a bug in SDAC with optimized storing of extended strings.
The manner in which some memory managers allocate headers of memory blocks differs from the standard memory manager bahaviour.
If you have no errors with SDAC in your project, there is no need to upgrade. Otherwise, we recommend you to upgrade to the last SDAC version.
The manner in which some memory managers allocate headers of memory blocks differs from the standard memory manager bahaviour.
If you have no errors with SDAC in your project, there is no need to upgrade. Otherwise, we recommend you to upgrade to the last SDAC version.
There is a property TCustomDADataSet.Options.FlatBuffers. It controls how dataset treats data of ftString and ftVarBytes fields. When set to True, all data fetched from the server is stored in record pdata without unused tails. When set to False, data of ftString and ftVarBytes fields with length more than 32 bytes is stored in preallocated memory blocks. Such fields are called "extended strings". Please see description of the FlatBuffers property in SDAC help for more information.