Release 1.1.1 - ETA 12.2025

Bugfixes​

Memory load when rendering large amounts of referenced entities​

Fixed excessive memory load with large amounts of data (>200.000 entities) combined with multiple large referenced entities resulting in 200.000 base entities and 1.000.000 referenced entities.

Squid can stream unlimited amounts of data and is only restricted by the system property glide.db.max_view_records as well as the Rest and JSON Catch All Transaction Quota Rule timeout settings.

Squid can be configured to render the same referenced entity with different target configurations, e.g. the reference field vendor is configured to be rendered with a targetConfig of core_company_minimal, while the reference field manufacturer is configured to be rendered with atargetConfig of core_company_full. It can and does occur that both vendor and manufacturer reference the same company, e.g. Apple. As Squid has conflicting target configurations, it retrieves the referenced entity multiple times, once for each targetConfig, merges the result and renders the merged object in the JSON section references.

Pre 1.1.1 Squid would cache referenced entities before merging them, potentially causing memory issues.

Squid now retrieves referenced entities in a way that causes zero memory load - without increasing the amount of database requests required.

Squid now only holds the sysIds of referenced entities in memory as well as any entities explicitly configured to be cached.