issue_comments
21 rows where "created_at" is on date 2021-06-19 sorted by created_at
This data as json, CSV (advanced)
Suggested facets: issue_url, updated_at (date)
id | html_url | issue_url | node_id | user | created_at ▼ | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
864328927 | https://github.com/simonw/sqlite-utils/issues/279#issuecomment-864328927 | https://api.github.com/repos/simonw/sqlite-utils/issues/279 | MDEyOklzc3VlQ29tbWVudDg2NDMyODkyNw== | simonw 9599 | 2021-06-19T00:25:08Z | 2021-06-19T00:25:17Z | OWNER | I tried writing this function with type hints, but eventually gave up:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils memory should handle TSV and JSON in addition to CSV 924990677 | |
864330508 | https://github.com/simonw/sqlite-utils/issues/279#issuecomment-864330508 | https://api.github.com/repos/simonw/sqlite-utils/issues/279 | MDEyOklzc3VlQ29tbWVudDg2NDMzMDUwOA== | simonw 9599 | 2021-06-19T00:34:24Z | 2021-06-19T00:34:24Z | OWNER | Got this working:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils memory should handle TSV and JSON in addition to CSV 924990677 | |
864348954 | https://github.com/simonw/sqlite-utils/issues/282#issuecomment-864348954 | https://api.github.com/repos/simonw/sqlite-utils/issues/282 | MDEyOklzc3VlQ29tbWVudDg2NDM0ODk1NA== | simonw 9599 | 2021-06-19T03:34:42Z | 2021-06-19T03:35:46Z | OWNER | I built some prototype code here for something which looks at every row in a CSV import and records the likely types: https://gist.github.com/simonw/465f9356f175d1cf86957947dff501d4 This could be used by the command-line tools to figure out what This is a different approach to the pure SQL version I tried building in https://github.com/simonw/sqlite-utils/issues/179 - I think this is a better approach though, it's less prone to weird idiosyncrasies of SQLite types, and it's also easy for us to add on to the existing CSV import code in a way that won't require scanning the data twice. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Automatic type detection for CSV data 925305186 | |
864349066 | https://github.com/simonw/sqlite-utils/issues/179#issuecomment-864349066 | https://api.github.com/repos/simonw/sqlite-utils/issues/179 | MDEyOklzc3VlQ29tbWVudDg2NDM0OTA2Ng== | simonw 9599 | 2021-06-19T03:36:04Z | 2021-06-19T03:36:04Z | OWNER | This work is going to happen in #282. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
sqlite-utils transform/insert --detect-types 709577625 | |
864349123 | https://github.com/simonw/sqlite-utils/issues/282#issuecomment-864349123 | https://api.github.com/repos/simonw/sqlite-utils/issues/282 | MDEyOklzc3VlQ29tbWVudDg2NDM0OTEyMw== | simonw 9599 | 2021-06-19T03:36:54Z | 2021-06-19T03:36:54Z | OWNER | I may change the default for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Automatic type detection for CSV data 925305186 | |
864350407 | https://github.com/simonw/sqlite-utils/issues/282#issuecomment-864350407 | https://api.github.com/repos/simonw/sqlite-utils/issues/282 | MDEyOklzc3VlQ29tbWVudDg2NDM1MDQwNw== | simonw 9599 | 2021-06-19T03:52:20Z | 2021-06-19T03:52:20Z | OWNER | I'll have an environment variable for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Automatic type detection for CSV data 925305186 | |
864354627 | https://github.com/simonw/sqlite-utils/issues/282#issuecomment-864354627 | https://api.github.com/repos/simonw/sqlite-utils/issues/282 | MDEyOklzc3VlQ29tbWVudDg2NDM1NDYyNw== | simonw 9599 | 2021-06-19T04:42:03Z | 2021-06-19T04:42:03Z | OWNER | Demo:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Automatic type detection for CSV data 925305186 | |
864358680 | https://github.com/simonw/sqlite-utils/issues/284#issuecomment-864358680 | https://api.github.com/repos/simonw/sqlite-utils/issues/284 | MDEyOklzc3VlQ29tbWVudDg2NDM1ODY4MA== | simonw 9599 | 2021-06-19T05:27:13Z | 2021-06-19T05:27:13Z | OWNER | How easy is it to detect a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.transform(types=) turns rowid into a concrete column 925320167 | |
864358951 | https://github.com/simonw/sqlite-utils/issues/284#issuecomment-864358951 | https://api.github.com/repos/simonw/sqlite-utils/issues/284 | MDEyOklzc3VlQ29tbWVudDg2NDM1ODk1MQ== | simonw 9599 | 2021-06-19T05:30:00Z | 2021-06-19T05:30:00Z | OWNER | If this can be fixed it will be in the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.transform(types=) turns rowid into a concrete column 925320167 | |
864416086 | https://github.com/simonw/sqlite-utils/issues/283#issuecomment-864416086 | https://api.github.com/repos/simonw/sqlite-utils/issues/283 | MDEyOklzc3VlQ29tbWVudDg2NDQxNjA4Ng== | simonw 9599 | 2021-06-19T14:49:06Z | 2021-06-19T14:49:13Z | OWNER | Once again, this is difficult because of the use of a generator here - I'm going to change |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
memory: Shouldn't detect types for JSON 925319214 | |
864416785 | https://github.com/simonw/sqlite-utils/issues/284#issuecomment-864416785 | https://api.github.com/repos/simonw/sqlite-utils/issues/284 | MDEyOklzc3VlQ29tbWVudDg2NDQxNjc4NQ== | simonw 9599 | 2021-06-19T14:54:41Z | 2021-06-19T14:54:41Z | OWNER | ```pycon <Table rowid_table (name)> >>> db["regular_table"].insert({"id": 1, "name": "Cleo"}, pk="id") <Table regular_table (id, name)> >>> db["rowid_table"].pks ['rowid'] >>> db["regular_table"].pks ['id'] ``` I think I need an introspection property for working out if a table is a `rowid` table or not. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.transform(types=) turns rowid into a concrete column 925320167 | |
864416911 | https://github.com/simonw/sqlite-utils/issues/284#issuecomment-864416911 | https://api.github.com/repos/simonw/sqlite-utils/issues/284 | MDEyOklzc3VlQ29tbWVudDg2NDQxNjkxMQ== | simonw 9599 | 2021-06-19T14:55:45Z | 2021-06-19T14:55:45Z | OWNER | So I can indeed detect a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.transform(types=) turns rowid into a concrete column 925320167 | |
864417031 | https://github.com/simonw/sqlite-utils/issues/285#issuecomment-864417031 | https://api.github.com/repos/simonw/sqlite-utils/issues/285 | MDEyOklzc3VlQ29tbWVudDg2NDQxNzAzMQ== | simonw 9599 | 2021-06-19T14:56:45Z | 2021-06-19T14:56:45Z | OWNER | ```pycon <Table rowid_table (name)> >>> db["regular_table"].insert({"id": 1, "name": "Cleo"}, pk="id") <Table regular_table (id, name)> >>> db["rowid_table"].pks ['rowid'] >>> db["regular_table"].pks ['id'] ``` But that's because the `.pks` property hides the difference: https://github.com/simonw/sqlite-utils/blob/dc94f4bb8cfe922bb2f9c89f8f0f29092ea63133/sqlite_utils/db.py#L805-L810 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Introspection property for telling if a table is a rowid table 925410305 | |
864417133 | https://github.com/simonw/sqlite-utils/issues/285#issuecomment-864417133 | https://api.github.com/repos/simonw/sqlite-utils/issues/285 | MDEyOklzc3VlQ29tbWVudDg2NDQxNzEzMw== | simonw 9599 | 2021-06-19T14:57:36Z | 2021-06-19T14:57:36Z | OWNER | So the logic is:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Introspection property for telling if a table is a rowid table 925410305 | |
864417493 | https://github.com/simonw/sqlite-utils/issues/285#issuecomment-864417493 | https://api.github.com/repos/simonw/sqlite-utils/issues/285 | MDEyOklzc3VlQ29tbWVudDg2NDQxNzQ5Mw== | simonw 9599 | 2021-06-19T15:00:43Z | 2021-06-19T15:00:43Z | OWNER | I have to be careful about the language I use here. Here's the official definition: https://www.sqlite.org/rowidtable.html
So it's not correct to call a table a "rowid table" only if it is missing its own primary keys. Maybe |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Introspection property for telling if a table is a rowid table 925410305 | |
864417765 | https://github.com/simonw/sqlite-utils/issues/285#issuecomment-864417765 | https://api.github.com/repos/simonw/sqlite-utils/issues/285 | MDEyOklzc3VlQ29tbWVudDg2NDQxNzc2NQ== | simonw 9599 | 2021-06-19T15:02:42Z | 2021-06-19T15:02:42Z | OWNER | Some options:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Introspection property for telling if a table is a rowid table 925410305 | |
864417808 | https://github.com/simonw/sqlite-utils/issues/285#issuecomment-864417808 | https://api.github.com/repos/simonw/sqlite-utils/issues/285 | MDEyOklzc3VlQ29tbWVudDg2NDQxNzgwOA== | simonw 9599 | 2021-06-19T15:03:00Z | 2021-06-19T15:03:00Z | OWNER | I think I like |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Introspection property for telling if a table is a rowid table 925410305 | |
864418188 | https://github.com/simonw/sqlite-utils/issues/285#issuecomment-864418188 | https://api.github.com/repos/simonw/sqlite-utils/issues/285 | MDEyOklzc3VlQ29tbWVudDg2NDQxODE4OA== | simonw 9599 | 2021-06-19T15:05:53Z | 2021-06-19T15:05:53Z | OWNER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Introspection property for telling if a table is a rowid table 925410305 | |
864418795 | https://github.com/simonw/sqlite-utils/issues/285#issuecomment-864418795 | https://api.github.com/repos/simonw/sqlite-utils/issues/285 | MDEyOklzc3VlQ29tbWVudDg2NDQxODc5NQ== | simonw 9599 | 2021-06-19T15:11:05Z | 2021-06-19T15:11:14Z | OWNER | Actually I'm going to go with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Introspection property for telling if a table is a rowid table 925410305 | |
864419283 | https://github.com/simonw/sqlite-utils/issues/284#issuecomment-864419283 | https://api.github.com/repos/simonw/sqlite-utils/issues/284 | MDEyOklzc3VlQ29tbWVudDg2NDQxOTI4Mw== | simonw 9599 | 2021-06-19T15:15:34Z | 2021-06-19T15:15:34Z | OWNER | I think this code is at fault: https://github.com/simonw/sqlite-utils/blob/5b257949d996fe43dc5d218d4308b88796a90740/sqlite_utils/db.py#L1017-L1023 It's using |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.transform(types=) turns rowid into a concrete column 925320167 | |
864476167 | https://github.com/simonw/sqlite-utils/issues/272#issuecomment-864476167 | https://api.github.com/repos/simonw/sqlite-utils/issues/272 | MDEyOklzc3VlQ29tbWVudDg2NDQ3NjE2Nw== | simonw 9599 | 2021-06-19T23:36:48Z | 2021-06-19T23:36:48Z | OWNER | Wrote this up on my blog here: https://simonwillison.net/2021/Jun/19/sqlite-utils-memory/ - with a video demo here: https://www.youtube.com/watch?v=OUjd0rkc678 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Idea: import CSV to memory, run SQL, export in a single command 921878733 |
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