issue_comments: 474890920
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/simonw/datasette/issues/422#issuecomment-474890920 | https://api.github.com/repos/simonw/datasette/issues/422 | 474890920 | MDEyOklzc3VlQ29tbWVudDQ3NDg5MDkyMA== | 9599 | 2019-03-20T15:39:58Z | 2019-03-20T15:39:58Z | OWNER | The page with the most table counts on it is the index page: https://fivethirtyeight.datasettes.com/fivethirtyeight-b76415d <img width="1032" alt="Screen Shot 2019-03-20 at 8 36 00 AM" src="https://user-images.githubusercontent.com/9599/54697753-5710ce80-4aeb-11e9-89aa-13f843a78d2c.png"> If I paginate this (which needs to happen anyway for Datasette Library #417) the impact here won't be as bad. I could even load in the table row counts asynchronously via JavaScript? Bigger problem is this total summed count representation on the homepage: <img width="1022" alt="Screen Shot 2019-03-20 at 8 38 53 AM" src="https://user-images.githubusercontent.com/9599/54697913-a3f4a500-4aeb-11e9-97a4-be501d737642.png"> I think that feature just won't be feasibly against large databases in a mutable world. Maybe we consider to show that total but only for immutable databases? May be easier just to drop it entirely (we will still show the table count). | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 423316403 |