We are currently working with a 1.8M dataset stored in MySQL. This table is indexed in multiple ways so it has potentially multiple fields by which to efficiently query and bring back records. Apologies for such basic questions, but we are looking for a bit of guidance on:
- The suggested approach to applying query parameters to one or more fields against this table that limits the dataset before reaching Appsheet. Security Filters? Slice + potential parameters?
- Ideally we would like to use pagination, but per our reading of the documentation and posts so far, this does not appear to be supported
1 Like
Security Filters are what you should be using to pull only certain records into the app.
Appsheet also allows the ability to load SQL “Views” in, instead of the entire Table.
I don’t know what you mean by “pagination”.
I also don’t know why you mention “Apify”.
1 Like
Apologies for the typo. Meant Appsheet.
In so far as the pagination, there is a common design pattern when dealing with large datasets in that only a given block (a page) of data is brought back from the database at a time. The user chooses to go to the next page of data or as the user scrolls down the table list more data is brought back. This prevents the need to load the entire data set.
1 Like
I see. Appsheet can only use Security Filters to limit data loaded, which are mostly based on the data present in the records. If you included a “page” column in your data, you could perhaps mimic the pagination by giving the user the ability to choose which pages to see. The following article might be of interest to you.
2 Likes