issue_comments
8 rows where "created_at" is on date 2021-06-22, "updated_at" is on date 2021-06-22 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url
user 1
- simonw · 8 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
865511810 | https://github.com/simonw/sqlite-utils/issues/290#issuecomment-865511810 | https://api.github.com/repos/simonw/sqlite-utils/issues/290 | MDEyOklzc3VlQ29tbWVudDg2NTUxMTgxMA== | simonw 9599 | 2021-06-22T04:07:34Z | 2021-06-22T18:26:21Z | OWNER | That documentation section is pretty weak at the moment - here's the whole thing:
It does at least cover the two types of parameters, though that could be bulked out. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`db.query()` method (renamed `db.execute_returning_dicts()`) 926777310 | |
866219755 | https://github.com/simonw/sqlite-utils/issues/289#issuecomment-866219755 | https://api.github.com/repos/simonw/sqlite-utils/issues/289 | MDEyOklzc3VlQ29tbWVudDg2NjIxOTc1NQ== | simonw 9599 | 2021-06-22T18:13:26Z | 2021-06-22T18:13:26Z | OWNER | Thanks @adamchainz - |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mypy fixes for rows_from_file() 925677191 | |
866184260 | https://github.com/simonw/sqlite-utils/issues/267#issuecomment-866184260 | https://api.github.com/repos/simonw/sqlite-utils/issues/267 | MDEyOklzc3VlQ29tbWVudDg2NjE4NDI2MA== | simonw 9599 | 2021-06-22T17:26:18Z | 2021-06-22T17:27:27Z | OWNER | If an |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
row.update() or row.pk 915421499 | |
866182655 | https://github.com/simonw/sqlite-utils/issues/267#issuecomment-866182655 | https://api.github.com/repos/simonw/sqlite-utils/issues/267 | MDEyOklzc3VlQ29tbWVudDg2NjE4MjY1NQ== | simonw 9599 | 2021-06-22T17:24:03Z | 2021-06-22T17:24:03Z | OWNER | I'm re-opening this as a research task because it may be possible to cleanly implement this using a Since this would just be for adding methods (and maybe a property for returning the primary keys for a row) the usual disadvantages of subclassing One catch: dictionaries already have a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
row.update() or row.pk 915421499 | |
865510796 | https://github.com/simonw/sqlite-utils/issues/290#issuecomment-865510796 | https://api.github.com/repos/simonw/sqlite-utils/issues/290 | MDEyOklzc3VlQ29tbWVudDg2NTUxMDc5Ng== | simonw 9599 | 2021-06-22T04:04:40Z | 2021-06-22T04:04:48Z | OWNER | Still needs documentation, which will involve rewriting the whole Executing queries section. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`db.query()` method (renamed `db.execute_returning_dicts()`) 926777310 | |
865497846 | https://github.com/simonw/sqlite-utils/issues/290#issuecomment-865497846 | https://api.github.com/repos/simonw/sqlite-utils/issues/290 | MDEyOklzc3VlQ29tbWVudDg2NTQ5Nzg0Ng== | simonw 9599 | 2021-06-22T03:21:38Z | 2021-06-22T03:21:38Z | OWNER | The Python docs say: https://docs.python.org/3/library/sqlite3.html
Looking at the C source code, both So it looks like the most efficient way to iterate over a cursor may well be |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`db.query()` method (renamed `db.execute_returning_dicts()`) 926777310 | |
865495370 | https://github.com/simonw/sqlite-utils/issues/290#issuecomment-865495370 | https://api.github.com/repos/simonw/sqlite-utils/issues/290 | MDEyOklzc3VlQ29tbWVudDg2NTQ5NTM3MA== | simonw 9599 | 2021-06-22T03:14:30Z | 2021-06-22T03:14:30Z | OWNER | One small problem with the existing method: https://github.com/simonw/sqlite-utils/blob/8cedc6a8b29180e68326f6b76f249d5e39e4b591/sqlite_utils/db.py#L362-L365 It returns a full list, but what if the user would rather have a generator they can iterate over without loading the results into memory in one go? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`db.query()` method (renamed `db.execute_returning_dicts()`) 926777310 | |
865491922 | https://github.com/simonw/sqlite-utils/issues/290#issuecomment-865491922 | https://api.github.com/repos/simonw/sqlite-utils/issues/290 | MDEyOklzc3VlQ29tbWVudDg2NTQ5MTkyMg== | simonw 9599 | 2021-06-22T03:05:35Z | 2021-06-22T03:05:35Z | OWNER | Potential names:
I think |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`db.query()` method (renamed `db.execute_returning_dicts()`) 926777310 |
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 3