issue_comments
11 rows where author_association = "OWNER", "created_at" is on date 2019-05-16 and reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw 11
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
493110184 | https://github.com/simonw/datasette/issues/419#issuecomment-493110184 | https://api.github.com/repos/simonw/datasette/issues/419 | MDEyOklzc3VlQ29tbWVudDQ5MzExMDE4NA== | simonw 9599 | 2019-05-16T15:14:31Z | 2019-05-16T15:14:31Z | OWNER | This is done bar the documentation, which is tracked in #421 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default to opening files in mutable mode, special option for immutable files 421551434 | |
493109347 | https://github.com/simonw/datasette/issues/418#issuecomment-493109347 | https://api.github.com/repos/simonw/datasette/issues/418 | MDEyOklzc3VlQ29tbWVudDQ5MzEwOTM0Nw== | simonw 9599 | 2019-05-16T15:12:26Z | 2019-05-16T15:12:26Z | OWNER | I'm ready to close this now thanks to fixing #471 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Hashed URLs should be optional 421548881 | |
493102841 | https://github.com/simonw/datasette/issues/471#issuecomment-493102841 | https://api.github.com/repos/simonw/datasette/issues/471 | MDEyOklzc3VlQ29tbWVudDQ5MzEwMjg0MQ== | simonw 9599 | 2019-05-16T14:56:50Z | 2019-05-16T15:10:11Z | OWNER | This is a good opportunity to add some missing test coverage for this feature. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
?_hash=1 and --config hash_urls:1 should only work for immutable databases 445003029 | |
492917925 | https://github.com/simonw/datasette/issues/464#issuecomment-492917925 | https://api.github.com/repos/simonw/datasette/issues/464 | MDEyOklzc3VlQ29tbWVudDQ5MjkxNzkyNQ== | simonw 9599 | 2019-05-16T05:04:35Z | 2019-05-16T05:04:35Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add Glitch to Getting Started docs section 443034218 | ||
492904704 | https://github.com/simonw/datasette/issues/465#issuecomment-492904704 | https://api.github.com/repos/simonw/datasette/issues/465 | MDEyOklzc3VlQ29tbWVudDQ5MjkwNDcwNA== | simonw 9599 | 2019-05-16T03:41:27Z | 2019-05-16T03:41:27Z | OWNER | The main use-case for this endpoint now is going to be Datasette Registry (which really needs some more love). That tool needs to be able to query a Datasette and find out:
A single Maybe a smarter approach will be the older idea of having a separate inspect for each database (and maybe each table):
Either way, I'm going to decouple this from milestone 0.28. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Decide what to do about /-/inspect 443038584 | |
492903581 | https://github.com/simonw/datasette/issues/460#issuecomment-492903581 | https://api.github.com/repos/simonw/datasette/issues/460 | MDEyOklzc3VlQ29tbWVudDQ5MjkwMzU4MQ== | simonw 9599 | 2019-05-16T03:34:08Z | 2019-05-16T03:34:08Z | OWNER | Demo of above: https://latest.datasette.io/?_sort=relationships compared to https://latest.datasette.io/ |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Design changes to homepage to support mutable files 443020810 | |
492903398 | https://github.com/simonw/datasette/issues/419#issuecomment-492903398 | https://api.github.com/repos/simonw/datasette/issues/419 | MDEyOklzc3VlQ29tbWVudDQ5MjkwMzM5OA== | simonw 9599 | 2019-05-16T03:33:01Z | 2019-05-16T03:33:01Z | OWNER | @russss sorry I only just spotted your comment here. I think I have an alternative suggestion for what you need to do here. It sounds to me like you need to calculate a specific piece of information against a specific database. Instead of doing this in inspect, how about having a separate tool which runs this once against the database file and writes the result into a database file there? I've been thinking about this pattern a bit as part of the sqlite-utils work I've been doing. It's already something that's needed for SQLite FTS support - it's no good just creating a FTS index, you have to populate it as well. In sqlite-utils world you do that like this: https://sqlite-utils.readthedocs.io/en/latest/cli.html#configuring-full-text-search
But then later if you've inserted new records you have to call this:
So one option here could be for Another option: Datasette now has an option to open a database file in "immutable" mode, using |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default to opening files in mutable mode, special option for immutable files 421551434 | |
492899100 | https://github.com/simonw/datasette/issues/460#issuecomment-492899100 | https://api.github.com/repos/simonw/datasette/issues/460 | MDEyOklzc3VlQ29tbWVudDQ5Mjg5OTEwMA== | simonw 9599 | 2019-05-16T03:07:41Z | 2019-05-16T03:07:41Z | OWNER | I'm going to sort by row counts first, but if row counts aren't available I'll fall back to number of inbound/outbound foreign keys. To make unit testing easier, I'll accept an undocumented ?_sort=relationships parameter |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Design changes to homepage to support mutable files 443020810 | |
492898595 | https://github.com/simonw/datasette/issues/460#issuecomment-492898595 | https://api.github.com/repos/simonw/datasette/issues/460 | MDEyOklzc3VlQ29tbWVudDQ5Mjg5ODU5NQ== | simonw 9599 | 2019-05-16T03:04:29Z | 2019-05-16T03:04:29Z | OWNER | One last thing before I close this: sort tables by number of inbound/outbound foreign keys. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Design changes to homepage to support mutable files 443020810 | |
492898241 | https://github.com/simonw/datasette/issues/467#issuecomment-492898241 | https://api.github.com/repos/simonw/datasette/issues/467 | MDEyOklzc3VlQ29tbWVudDQ5Mjg5ODI0MQ== | simonw 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 } |
Index page row counts only for DBs with < 30 tables (10ms count limit per table) 444711254 | |
492883561 | https://github.com/simonw/datasette/issues/467#issuecomment-492883561 | https://api.github.com/repos/simonw/datasette/issues/467 | MDEyOklzc3VlQ29tbWVudDQ5Mjg4MzU2MQ== | simonw 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 } |
Index page row counts only for DBs with < 30 tables (10ms count limit per table) 444711254 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [issue] INTEGER REFERENCES [issues]([id]) , [performed_via_github_app] TEXT); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
issue 7