You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2021/01/26 11:35:09 UTC

[GitHub] [superset] bolkedebruin commented on issue #7804: Server side pagination for charts (tables)

bolkedebruin commented on issue #7804:
URL: https://github.com/apache/superset/issues/7804#issuecomment-767485225


   @mistercrunch @frafra The typical way to solve this is to rely on a primary key or on a index and remember where you left off. In mariadb terms `SELECT ... WHERE ... AND id < $left_off ORDER BY id DESC LIMIT 100`. This allows the database to mak use of the physical layout of the data on disk and is extremely efficient. There is probably no need to cache the result even in case of traditional rdbms (e.g. Postgres, Mysql; Hive/Presto you do want to cache due to query lead times)
   
   So what could be possible is to enable server side pagination for tables that have a primary key or an index and disable it for tables that don’t.
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org