Is there a way to send filter & sort operations to server side ?
GQI is nice to do some custom queries but the inconvenient is once you want to integrate it in a table, you have to send the whole table data to have filtering & sorting.
This start to be a problem when you have thousands of rows in your table.
Sending to server side would necessit to code the filter ourselves but it is something common in other frameworks or languages.
For example, js component datatables.net (DataTables | Javascript table library ) is a component which let you choose if you want to process data on client side or server side.
I wish something similar could exist to be able to use the GQI queries on large amount of data.
Hello Ward,
it is an ad hoc data source provided by GQI.
i agree it is our responsability to fetch the data as efficient as possible but when using in a table it is not easy as filter and sorting are done on client side.
currently if we use an adhoc data source to fill a table, the fetch process ask every page until GetNextPage returns false.
Do you know in which version the feature you mention will be released ?
Hi Julien,
Could you elaborate on the data source you are using? (Is it a built-in one or are you creating your own ad hoc data source?)
If you sort or filter the data within your table (using the column header of the table) than a sort or filter operator will be appended to the query behind the scenes.
Most built-in data sources are optimized as such that filter and sort operators are forwarded to the server, to ensure an efficient and scalable data retrieval.
For ad-hoc data sources it is the responsibility of the ad-hoc data source creator to fetch the data as efficient as possible, to make it scalable. For that they can use paging, caching etc. We currently also have a feature on our backlog to expose information about the query to the ad-hoc data source implementation. (For example, which filters are applied etc.)
Best regards, Ward
Hi Julien, thank you for providing me with some more info!
If your query is shown in a table than it should not necessarely fetch all pages. Since GQI will only retrieve just about enough rows to fill the table. If you scroll down additional pages are fetched from your ad hoc data source.
If the query contains some operators such as aggregate, join, sort etc. Than it might occur that all pages are fetched from your ad hoc data source in order to fill the first visible rows in your table. For example, we need all the data to be able to correctly sort the data.
I currently have no ETA for that feature, it is currently on our backlog, I will include your question/use case to boost the priority.
Best regards, Ward