issue_comments

Table actions

20 rows where "updated_at" is on date 2022-01-26 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: issue_url, reactions, created_at (date), updated_at (date)

user 1

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1022466476 https://github.com/simonw/sqlite-utils/issues/392#issuecomment-1022466476 https://api.github.com/repos/simonw/sqlite-utils/issues/392 IC_kwDOCGYnMM488Zms simonw 9599 2022-01-26T18:17:43Z 2022-01-26T18:17:43Z OWNER

Manually tested it like this: ```

Create database with an empty "lines" table

sqlite-utils create-table bulk-test.db lines line text

Stream records every 0.5s, commit every 5 records

stream-delay docs/python-api.rst -d 500 | \ sqlite-utils bulk bulk-test.db 'insert into lines (line) values (:line)' - \ --lines --batch-size 5 `` Runningdatasette bulk-test.db` showed that records would show up about every 2.5s five at a time.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `sqlite-utils bulk --batch-size` option 1114640101  
1022381732 https://github.com/simonw/datasette/issues/1613#issuecomment-1022381732 https://api.github.com/repos/simonw/datasette/issues/1613 IC_kwDOBm6k_c488E6k simonw 9599 2022-01-26T16:41:45Z 2022-01-26T16:41:45Z OWNER

A better interface for modifying the columns used in the SELECT clause would be useful too.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Improvements to help make Datasette a better tool for learning SQL 1114628238  
1022255862 https://github.com/simonw/datasette/issues/1613#issuecomment-1022255862 https://api.github.com/repos/simonw/datasette/issues/1613 IC_kwDOBm6k_c487mL2 simonw 9599 2022-01-26T14:35:31Z 2022-01-26T14:37:44Z OWNER

Joins are really hard. A mechanism for constructing them in the table view would help a lot: - https://github.com/simonw/datasette/issues/613

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Improvements to help make Datasette a better tool for learning SQL 1114628238  
1022254258 https://github.com/simonw/datasette/issues/1613#issuecomment-1022254258 https://api.github.com/repos/simonw/datasette/issues/1613 IC_kwDOBm6k_c487lyy simonw 9599 2022-01-26T14:33:46Z 2022-01-26T14:37:31Z OWNER

Tool for setting up foreign key relationships. It could even verify the relationship before you apply it - checking that every value in the column does indeed correspond to a value in the other table.

Could also detect and suggest possible ones.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Improvements to help make Datasette a better tool for learning SQL 1114628238  
1022257496 https://github.com/simonw/datasette/issues/1613#issuecomment-1022257496 https://api.github.com/repos/simonw/datasette/issues/1613 IC_kwDOBm6k_c487mlY simonw 9599 2022-01-26T14:37:14Z 2022-01-26T14:37:14Z OWNER

Better contextual help on the SQL editor - like in Django SQL Dashboard which shows all available tables and columns.

Fancy inline autocomplete would be great too, but that's pretty hard for SQL based on past research.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Improvements to help make Datasette a better tool for learning SQL 1114628238  
1021877769 https://github.com/simonw/sqlite-utils/issues/392#issuecomment-1021877769 https://api.github.com/repos/simonw/sqlite-utils/issues/392 IC_kwDOCGYnMM486J4J simonw 9599 2022-01-26T05:19:48Z 2022-01-26T05:19:48Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `sqlite-utils bulk --batch-size` option 1114640101  
1021877058 https://github.com/simonw/sqlite-utils/issues/392#issuecomment-1021877058 https://api.github.com/repos/simonw/sqlite-utils/issues/392 IC_kwDOCGYnMM486JtC simonw 9599 2022-01-26T05:18:12Z 2022-01-26T05:18:18Z OWNER

Help for insert says: --batch-size INTEGER Commit every X records

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `sqlite-utils bulk --batch-size` option 1114640101  
1021876914 https://github.com/simonw/sqlite-utils/issues/392#issuecomment-1021876914 https://api.github.com/repos/simonw/sqlite-utils/issues/392 IC_kwDOCGYnMM486Jqy simonw 9599 2022-01-26T05:17:49Z 2022-01-26T05:17:49Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `sqlite-utils bulk --batch-size` option 1114640101  
1021876463 https://github.com/simonw/sqlite-utils/issues/391#issuecomment-1021876463 https://api.github.com/repos/simonw/sqlite-utils/issues/391 IC_kwDOCGYnMM486Jjv simonw 9599 2022-01-26T05:16:51Z 2022-01-26T05:16:51Z OWNER

Actually adding a progress bar may not make sense here: it's designed to work with streaming input from stdin, in which case it's impossible for it to know the overall number of rows to be processed.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `sqlite-utils bulk` progress bar 1114638930  
1021876055 https://github.com/simonw/sqlite-utils/issues/391#issuecomment-1021876055 https://api.github.com/repos/simonw/sqlite-utils/issues/391 IC_kwDOCGYnMM486JdX simonw 9599 2022-01-26T05:15:58Z 2022-01-26T05:15:58Z OWNER

Could add support for --batch-size as seen in insert/upsert too - causing it to break the list up into batches and commit for each one.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `sqlite-utils bulk` progress bar 1114638930  
1021860694 https://github.com/simonw/datasette/issues/1613#issuecomment-1021860694 https://api.github.com/repos/simonw/datasette/issues/1613 IC_kwDOBm6k_c486FtW simonw 9599 2022-01-26T04:57:53Z 2022-01-26T04:57:53Z OWNER

The existing flow where you can apply filters to a table and then click "View and edit SQL" to see the query is a good starting point.

Group by queries are both crucially important and difficult to assemble for beginners. Providing a way to see the query that was used by a facet (since facets are really just group-by-counts) would be very useful, which could come out of this:

  • 1080

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Improvements to help make Datasette a better tool for learning SQL 1114628238  
1021825322 https://github.com/simonw/sqlite-utils/issues/390#issuecomment-1021825322 https://api.github.com/repos/simonw/sqlite-utils/issues/390 IC_kwDOCGYnMM4859Eq simonw 9599 2022-01-26T03:20:12Z 2022-01-26T03:20:25Z OWNER

``` % sqlite-utils upsert trees.db blah - Usage: sqlite-utils upsert [OPTIONS] PATH TABLE FILE Try 'sqlite-utils upsert -h' for help.

Error: Missing option '--pk'. ```

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 `sqlite-utils upsert` should require `--pk` more elegantly 1114557284  
1021790707 https://github.com/simonw/sqlite-utils/issues/48#issuecomment-1021790707 https://api.github.com/repos/simonw/sqlite-utils/issues/48 IC_kwDOCGYnMM4850nz simonw 9599 2022-01-26T02:08:39Z 2022-01-26T02:08:39Z OWNER

This is a dupe of #308.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Jupyter notebook demo of the library, launchable on Binder 471818939  
1021790136 https://github.com/simonw/sqlite-utils/issues/389#issuecomment-1021790136 https://api.github.com/repos/simonw/sqlite-utils/issues/389 IC_kwDOCGYnMM4850e4 simonw 9599 2022-01-26T02:07:41Z 2022-01-26T02:07:41Z OWNER

That fixed it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Plausible analytics for documentation 1114544727  
1021789016 https://github.com/simonw/sqlite-utils/issues/389#issuecomment-1021789016 https://api.github.com/repos/simonw/sqlite-utils/issues/389 IC_kwDOCGYnMM4850NY simonw 9599 2022-01-26T02:05:41Z 2022-01-26T02:05:41Z OWNER

Oops, wrong domain in that - https://plausible.io/sqlite-utils.datasette.io is not yet showing data.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Plausible analytics for documentation 1114544727  
1021788260 https://github.com/simonw/sqlite-utils/issues/388#issuecomment-1021788260 https://api.github.com/repos/simonw/sqlite-utils/issues/388 IC_kwDOCGYnMM4850Bk simonw 9599 2022-01-26T02:04:17Z 2022-01-26T02:04:17Z OWNER

https://sqlite-utils.datasette.io/en/3.20/ now also shows the version warning banner.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Link to stable docs from older versions 1114543475  
1021787822 https://github.com/simonw/sqlite-utils/issues/388#issuecomment-1021787822 https://api.github.com/repos/simonw/sqlite-utils/issues/388 IC_kwDOCGYnMM485z6u simonw 9599 2022-01-26T02:03:25Z 2022-01-26T02:03:25Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Link to stable docs from older versions 1114543475  
1021785268 https://github.com/simonw/sqlite-utils/issues/388#issuecomment-1021785268 https://api.github.com/repos/simonw/sqlite-utils/issues/388 IC_kwDOCGYnMM485zS0 simonw 9599 2022-01-26T01:58:19Z 2022-01-26T01:58:19Z OWNER

While I'm modifying that template I'm also going to add Plausible analytics: ```html

<script defer data-domain="sqlite-utils.datasette.io" src="https://plausible.io/js/plausible.js"></script>

```

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Link to stable docs from older versions 1114543475  
1021784593 https://github.com/simonw/sqlite-utils/issues/388#issuecomment-1021784593 https://api.github.com/repos/simonw/sqlite-utils/issues/388 IC_kwDOCGYnMM485zIR simonw 9599 2022-01-26T01:56:48Z 2022-01-26T01:56:48Z OWNER

On https://readthedocs.org/dashboard/sqlite-utils/advanced/ I checked this box (previously unchecked):

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Link to stable docs from older versions 1114543475  
1021773056 https://github.com/simonw/sqlite-utils/issues/387#issuecomment-1021773056 https://api.github.com/repos/simonw/sqlite-utils/issues/387 IC_kwDOCGYnMM485wUA simonw 9599 2022-01-26T01:37:17Z 2022-01-26T01:37:17Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Python library docs should start with a self contained example 1111293050  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);