github
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/467#issuecomment-492898241 | https://api.github.com/repos/simonw/datasette/issues/467 | 492898241 | MDEyOklzc3VlQ29tbWVudDQ5Mjg5ODI0MQ== | 9599 | 2019-05-16T03:02:27Z | 2019-05-16T03:02:27Z | OWNER | I'm going to be lazy and skip the unit test for this, because I don't currently have a neat way of mocking a SQL interrupted exception to simulate a query taking too long (at least for these counts). | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
444711254 | |
https://github.com/simonw/datasette/issues/467#issuecomment-492883561 | https://api.github.com/repos/simonw/datasette/issues/467 | 492883561 | MDEyOklzc3VlQ29tbWVudDQ5Mjg4MzU2MQ== | 9599 | 2019-05-16T01:40:09Z | 2019-05-16T01:40:09Z | OWNER | I'm setting X to 30 because the fixtures database currently has 26 tables (22 visible, 4 hidden) and I want to display counts for it. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
444711254 |