Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paginate + search for databases/tables on the homepage #461

Open
Tracked by #2456
simonw opened this issue May 11, 2019 · 4 comments
Open
Tracked by #2456

Paginate + search for databases/tables on the homepage #461

simonw opened this issue May 11, 2019 · 4 comments

Comments

@simonw
Copy link
Owner

simonw commented May 11, 2019

Split out from #460 - in order to support large numbers of connected databases the homepage needs to be paginated.

@simonw simonw added the feature label May 11, 2019
@simonw
Copy link
Owner Author

simonw commented May 11, 2019

I plan to add a search filter box too, but only if there are more than X (probably 10) connected databases.

@simonw
Copy link
Owner Author

simonw commented May 14, 2019

This is needed by Datasette Library #417 since that's going to demand listing a LOT of databases on the homepage.

@simonw
Copy link
Owner Author

simonw commented Oct 16, 2020

Related: redesign homepage entirely #991.

@simonw simonw added this to the Datasette 1.0 milestone Oct 16, 2020
@simonw simonw changed the title Paginate + search for databases on the homepage Paginate + search for databases/tables on the homepage Oct 17, 2020
@simonw
Copy link
Owner Author

simonw commented Dec 17, 2020

I've been thinking about this a bunch. For Datasette to be useful as a private repository of data (Datasette Library, #417) it's crucial that it can handle a much, much larger number of databases.

This makes me worry about how many connections (and open file handles) it makes sense to have open at one time.

I realize now that this is much less of a problem for private instances. Public instances on the internet could get traffic to any database at any time, so connections could easily get out of control. A private instance with only a few users could instead get away with only opening connections to databases in "active use".

This does however make it even more important for Datasette to maintain a cached set of metadata about the tables - which is also needed to power this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant