The current application logic fetches the table list on boot and refreshes the result set in certain situations (i.e. after a DDL type query). This is fine, unless the user has a lot of tables in the database (1000+), in which case the application can become unstable or stop working altogether.
To fix the problem, the tables() query has to be paginated. There is a number of things that have to be done in the application logic:
[ ] Add method to fetch tables with LIMIT or WHERE filter
[ ] LIMIT for table listing
[ ] WHERE for FIlter search bar
[ ] Refactor Tables UI to paginate table results
[ ] Refactor Filter search bar to use SQL filter when searching
[ ] Refactor Create Table to use search on demand when validating if a given table name exists already
[ ] WHERE for checking table existence in Import CSV
The current application logic fetches the table list on boot and refreshes the result set in certain situations (i.e. after a DDL type query). This is fine, unless the user has a lot of tables in the database (1000+), in which case the application can become unstable or stop working altogether.
To fix the problem, the
tables()query has to be paginated. There is a number of things that have to be done in the application logic:WHEREfor checking table existence in Import CSV