native-query-filter

Speed up TypeORM dynamic lists by offloading complex filtering and pagination to native SQL via get_filtered_list, returning filtered data and total counts efficiently on large datasets.

The best way to build admin endpoints with multi-join filtering is using a config-driven whitelist of allowed keys combined with native SQL, ensuring secure query construction and fast responses.

Yes, the native SQL filter approach works with sanitized DTO-based filters by passing a filters map to get_filtered_list alongside a YAML/JSON entity configuration to ensure predictable query construction.

Configure TypeORM entities by defining a YAML/JSON config file for allowed filter keys, then load it with FilteredListBuilder and call get_filtered_list(p_config, p_filters, p_pagination) to retrieve results.

Use native SQL instead of ORM when endpoints require complex filtering, pagination, and joins where ORM alone is insufficient or slow, specifically optimizing large dataset responses.

Yes, you can get total counts alongside filtered data by calling the native SQL get_filtered_list function, which returns both the filtered dataset and the total_count for pagination.