When fetching records via the cache, records were not written immediately to the cache. Instead, the cache was hooked up via the writeback mechanism.
This was way too slow, especially for complicated records like torsiondrive. So now we write them immediately. Records currently don't have proper change tracking, so any modifications to the record won't be reflected in the cache, but that should be added someday.
Description
When fetching records via the cache, records were not written immediately to the cache. Instead, the cache was hooked up via the writeback mechanism.
This was way too slow, especially for complicated records like torsiondrive. So now we write them immediately. Records currently don't have proper change tracking, so any modifications to the record won't be reflected in the cache, but that should be added someday.
Status