Hello folks!
From the REST API, does anyone know if it’s more efficient to call a BAQ with parameters or call a non-paramterized BAQ using the oData $filter query option?
Thanks!
I think it depends on how the BAQ is structured.
I think the where (filter) clauses are passed down to the BAQ call itself and combined, but that won’t always be helpful.
2 Likes
In cases where the full return data will contain so many rows that storing the data in memory will cause slowdowns, or when excluding the where clause / parameters will cause the query execution time to be noticeably longer, I would use the parameters. Otherwise I would use the $filter.
2 Likes
I think this sounds like what I wanted to know … the parameters operate IN the query on the DB side, and the OData $fllter is post data processing before delivery. Sound about right?
Basically if I want to be a good database citizen (as a cloud customer), I should go the parameterized route (if possible).
1 Like