{"html_url": "https://github.com/simonw/datasette/issues/1818#issuecomment-1258738740", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/1818", "id": 1258738740, "node_id": "IC_kwDOBm6k_c5LBtQ0", "user": {"value": 5363, "label": "nelsonjchen"}, "created_at": "2022-09-26T22:52:45Z", "updated_at": "2022-09-26T22:55:57Z", "author_association": "NONE", "body": "thoughts on order of precedence to use:\r\n\r\n* sqlite-utils count, if present. closest thing to a standard i guess.\r\n* row(max_id) if like, the first and/or last x amount of rows ids are all contiguous. kind of a cheap/dumb/imperfect heuristic to see if the table is dump/not dump. if the check passes, still stick on `est.` after the display.\r\n* count(*) if enabled in datasette ", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 1384549993, "label": "Setting to turn off table row counts entirely"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/1818#issuecomment-1258735747", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/1818", "id": 1258735747, "node_id": "IC_kwDOBm6k_c5LBsiD", "user": {"value": 9599, "label": "simonw"}, "created_at": "2022-09-26T22:47:59Z", "updated_at": "2022-09-26T22:47:59Z", "author_association": "OWNER", "body": "Another option here is to tie into a feature I built in `sqlite-utils` with this problem in mind but never introduced on the Datasette side of things: https://sqlite-utils.datasette.io/en/stable/python-api.html#cached-table-counts-using-triggers", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 1384549993, "label": "Setting to turn off table row counts entirely"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/1818#issuecomment-1258735283", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/1818", "id": 1258735283, "node_id": "IC_kwDOBm6k_c5LBsaz", "user": {"value": 9599, "label": "simonw"}, "created_at": "2022-09-26T22:47:19Z", "updated_at": "2022-09-26T22:47:19Z", "author_association": "OWNER", "body": "That's a really interesting idea: for a lot of databases (those made out of straight imports from CSV) `max(rowid)` would indeed reflect the size of the table, but would be a MUCH faster operation than attempting a `count(*)`.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 1384549993, "label": "Setting to turn off table row counts entirely"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/1818#issuecomment-1257290709", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/1818", "id": 1257290709, "node_id": "IC_kwDOBm6k_c5K8LvV", "user": {"value": 5363, "label": "nelsonjchen"}, "created_at": "2022-09-25T22:17:06Z", "updated_at": "2022-09-25T22:17:06Z", "author_association": "NONE", "body": "I wonder if having an option for displaying the max row id might help too. Not accurate especially if something was deleted, but useful for DBs as a dump. ", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 1384549993, "label": "Setting to turn off table row counts entirely"}, "performed_via_github_app": null}