issue_comments
18 rows where author_association = "OWNER", reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}", "updated_at" is on date 2020-09-07 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
user 1
- simonw · 18 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
688544156 | https://github.com/simonw/sqlite-utils/issues/154#issuecomment-688544156 | https://api.github.com/repos/simonw/sqlite-utils/issues/154 | MDEyOklzc3VlQ29tbWVudDY4ODU0NDE1Ng== | simonw 9599 | 2020-09-07T23:47:10Z | 2020-09-07T23:47:10Z | OWNER | This is already covered in the tests though: https://github.com/simonw/sqlite-utils/blob/deb2eb013ff85bbc828ebc244a9654f0d9c3139e/tests/test_cli.py#L1300-L1328 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
OperationalError: cannot change into wal mode from within a transaction 695441530 | |
688543128 | https://github.com/simonw/sqlite-utils/issues/154#issuecomment-688543128 | https://api.github.com/repos/simonw/sqlite-utils/issues/154 | MDEyOklzc3VlQ29tbWVudDY4ODU0MzEyOA== | simonw 9599 | 2020-09-07T23:43:10Z | 2020-09-07T23:43:10Z | OWNER | Running this against the same file works:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
OperationalError: cannot change into wal mode from within a transaction 695441530 | |
688500704 | https://github.com/simonw/sqlite-utils/issues/152#issuecomment-688500704 | https://api.github.com/repos/simonw/sqlite-utils/issues/152 | MDEyOklzc3VlQ29tbWVudDY4ODUwMDcwNA== | simonw 9599 | 2020-09-07T20:28:45Z | 2020-09-07T21:17:48Z | OWNER | The principle reason to turn these on - at least so far - is that without it weird things happen where FTS tables (in particular |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Turn on recursive_triggers by default 695376054 | |
688511161 | https://github.com/simonw/sqlite-utils/issues/153#issuecomment-688511161 | https://api.github.com/repos/simonw/sqlite-utils/issues/153 | MDEyOklzc3VlQ29tbWVudDY4ODUxMTE2MQ== | simonw 9599 | 2020-09-07T21:07:20Z | 2020-09-07T21:07:29Z | OWNER | FTS4 uses a different column name here: https://datasette-sqlite-fts4.datasette.io/24ways-fts4/articles_fts_docsize
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
table.optimize() should delete junk rows from *_fts_docsize 695377804 | |
688508510 | https://github.com/simonw/sqlite-utils/pull/146#issuecomment-688508510 | https://api.github.com/repos/simonw/sqlite-utils/issues/146 | MDEyOklzc3VlQ29tbWVudDY4ODUwODUxMA== | simonw 9599 | 2020-09-07T20:56:03Z | 2020-09-07T20:56:24Z | OWNER | The problem with this approach is that it requires us to consume the entire iterator before we can start inserting rows into the table - here on line 1052: I designed the
So we need to solve this issue without consuming the entire iterator with a I think one way to do this is to execute each chunk one at a time and watch out for an exception that indicates that we sent too many parameters - then adjust the chunk size down and try again. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Handle case where subsequent records (after first batch) include extra columns 688668680 | |
688506015 | https://github.com/simonw/sqlite-utils/issues/153#issuecomment-688506015 | https://api.github.com/repos/simonw/sqlite-utils/issues/153 | MDEyOklzc3VlQ29tbWVudDY4ODUwNjAxNQ== | simonw 9599 | 2020-09-07T20:46:58Z | 2020-09-07T20:46:58Z | OWNER | Writing a test for this will be a tiny bit tricky. I think I'll use a test that replicates the bug in #149. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
table.optimize() should delete junk rows from *_fts_docsize 695377804 | |
688501064 | https://github.com/simonw/sqlite-utils/issues/149#issuecomment-688501064 | https://api.github.com/repos/simonw/sqlite-utils/issues/149 | MDEyOklzc3VlQ29tbWVudDY4ODUwMTA2NA== | simonw 9599 | 2020-09-07T20:30:15Z | 2020-09-07T20:30:38Z | OWNER | The second challenge here is cleaning up all of those junk rows in existing |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
FTS table with 7 rows has _fts_docsize table with 9,141 rows 695319258 | |
688500294 | https://github.com/simonw/sqlite-utils/issues/152#issuecomment-688500294 | https://api.github.com/repos/simonw/sqlite-utils/issues/152 | MDEyOklzc3VlQ29tbWVudDY4ODUwMDI5NA== | simonw 9599 | 2020-09-07T20:27:07Z | 2020-09-07T20:27:07Z | OWNER | I'm going to make this an argument to the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Turn on recursive_triggers by default 695376054 | |
688499924 | https://github.com/simonw/sqlite-utils/issues/149#issuecomment-688499924 | https://api.github.com/repos/simonw/sqlite-utils/issues/149 | MDEyOklzc3VlQ29tbWVudDY4ODQ5OTkyNA== | simonw 9599 | 2020-09-07T20:25:40Z | 2020-09-07T20:25:50Z | OWNER | https://www.sqlite.org/pragma.html#pragma_recursive_triggers says:
So I think the fix is to turn on |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
FTS table with 7 rows has _fts_docsize table with 9,141 rows 695319258 | |
688499650 | https://github.com/simonw/sqlite-utils/issues/149#issuecomment-688499650 | https://api.github.com/repos/simonw/sqlite-utils/issues/149 | MDEyOklzc3VlQ29tbWVudDY4ODQ5OTY1MA== | simonw 9599 | 2020-09-07T20:24:35Z | 2020-09-07T20:24:35Z | OWNER | This replicates the problem:
The number went up by ten. I used tracing from #151 to show that the following SQL executed ten times:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
FTS table with 7 rows has _fts_docsize table with 9,141 rows 695319258 | |
688482355 | https://github.com/simonw/sqlite-utils/issues/149#issuecomment-688482355 | https://api.github.com/repos/simonw/sqlite-utils/issues/149 | MDEyOklzc3VlQ29tbWVudDY4ODQ4MjM1NQ== | simonw 9599 | 2020-09-07T19:22:51Z | 2020-09-07T19:22:51Z | OWNER | And the SQLite documentation says:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
FTS table with 7 rows has _fts_docsize table with 9,141 rows 695319258 | |
688482055 | https://github.com/simonw/sqlite-utils/issues/149#issuecomment-688482055 | https://api.github.com/repos/simonw/sqlite-utils/issues/149 | MDEyOklzc3VlQ29tbWVudDY4ODQ4MjA1NQ== | simonw 9599 | 2020-09-07T19:21:42Z | 2020-09-07T19:21:42Z | OWNER | Using
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
FTS table with 7 rows has _fts_docsize table with 9,141 rows 695319258 | |
688481374 | https://github.com/simonw/sqlite-utils/issues/149#issuecomment-688481374 | https://api.github.com/repos/simonw/sqlite-utils/issues/149 | MDEyOklzc3VlQ29tbWVudDY4ODQ4MTM3NA== | simonw 9599 | 2020-09-07T19:19:08Z | 2020-09-07T19:19:08Z | OWNER | reading through the code for
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
FTS table with 7 rows has _fts_docsize table with 9,141 rows 695319258 | |
688480665 | https://github.com/simonw/sqlite-utils/issues/149#issuecomment-688480665 | https://api.github.com/repos/simonw/sqlite-utils/issues/149 | MDEyOklzc3VlQ29tbWVudDY4ODQ4MDY2NQ== | simonw 9599 | 2020-09-07T19:16:20Z | 2020-09-07T19:16:20Z | OWNER | Aha! I have managed to replicate the bug:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
FTS table with 7 rows has _fts_docsize table with 9,141 rows 695319258 | |
688464181 | https://github.com/simonw/sqlite-utils/issues/149#issuecomment-688464181 | https://api.github.com/repos/simonw/sqlite-utils/issues/149 | MDEyOklzc3VlQ29tbWVudDY4ODQ2NDE4MQ== | simonw 9599 | 2020-09-07T18:19:54Z | 2020-09-07T18:19:54Z | OWNER | Even though that table doesn't declare an integer primary key it does have a | rowid | key | name | spdx_id | url | node_id | | --- | --- | --- | --- | --- | --- | | 9150 | apache-2.0 | Apache License 2.0 | Apache-2.0 | https://api.github.com/licenses/apache-2.0 | MDc6TGljZW5zZTI= | | 112 | bsd-3-clause | BSD 3-Clause "New" or "Revised" License | BSD-3-Clause | https://api.github.com/licenses/bsd-3-clause | MDc6TGljZW5zZTU= | https://www.sqlite.org/rowidtable.html explains has this clue:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
FTS table with 7 rows has _fts_docsize table with 9,141 rows 695319258 | |
688460865 | https://github.com/simonw/sqlite-utils/issues/149#issuecomment-688460865 | https://api.github.com/repos/simonw/sqlite-utils/issues/149 | MDEyOklzc3VlQ29tbWVudDY4ODQ2MDg2NQ== | simonw 9599 | 2020-09-07T18:07:14Z | 2020-09-07T18:07:14Z | OWNER | Another likely culprit: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
FTS table with 7 rows has _fts_docsize table with 9,141 rows 695319258 | |
688460729 | https://github.com/simonw/sqlite-utils/issues/149#issuecomment-688460729 | https://api.github.com/repos/simonw/sqlite-utils/issues/149 | MDEyOklzc3VlQ29tbWVudDY4ODQ2MDcyOQ== | simonw 9599 | 2020-09-07T18:06:44Z | 2020-09-07T18:06:44Z | OWNER | First posted on SQLite forum here but I'm pretty sure this is a bug in how |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
FTS table with 7 rows has _fts_docsize table with 9,141 rows 695319258 | |
688434226 | https://github.com/simonw/sqlite-utils/issues/148#issuecomment-688434226 | https://api.github.com/repos/simonw/sqlite-utils/issues/148 | MDEyOklzc3VlQ29tbWVudDY4ODQzNDIyNg== | simonw 9599 | 2020-09-07T16:50:33Z | 2020-09-07T16:50:33Z | OWNER | This may be as easy as applying I could apply that to a few other queries in that code as well. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
More attractive indentation of created FTS table schema 695276328 |
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 6