issue_comments: 513244121
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/simonw/sqlite-utils/issues/42#issuecomment-513244121 | https://api.github.com/repos/simonw/sqlite-utils/issues/42 | 513244121 | MDEyOklzc3VlQ29tbWVudDUxMzI0NDEyMQ== | 9599 | 2019-07-19T14:13:33Z | 2019-07-19T14:13:33Z | OWNER | So what could the interface to this look like? Especially for the CLI? One option:
Tricky thing here is that it's quite a large number of positional arguments:
It would be great if this could supported multiple columns - for if a spreadsheet has e.g. a “Company Name”, “Company Address” pair of fields that always match each other and areduplicated many times. This could be handled by creating the new table with two columns that are indexed as a unique compound key. Then you can easily get-or-create on the pairs (or triples or whatever) from the original table. Challenge here is what does the CLI syntax look like. Something like this?
Perhaps the columns in the new table are FORCED to be the same as the old ones, hence avoiding some options? Bit restrictive… maybe they default to the same but you can customize?
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
470345929 |