github
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/272#issuecomment-861891835 | https://api.github.com/repos/simonw/sqlite-utils/issues/272 | 861891835 | MDEyOklzc3VlQ29tbWVudDg2MTg5MTgzNQ== | 9599 | 2021-06-15T23:09:31Z | 2021-06-15T23:09:31Z | OWNER | `--load-csv` and `--load-json` and `--load-nl` and `--load-tsv` are unambiguous. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
921878733 | |
https://github.com/simonw/sqlite-utils/issues/272#issuecomment-861891693 | https://api.github.com/repos/simonw/sqlite-utils/issues/272 | 861891693 | MDEyOklzc3VlQ29tbWVudDg2MTg5MTY5Mw== | 9599 | 2021-06-15T23:09:08Z | 2021-06-15T23:09:08Z | OWNER | Problem: `--csv` and `--json` and `--nl` are already options for `sqlite-utils query` - need new non-conflicting names. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
921878733 | |
https://github.com/simonw/sqlite-utils/issues/272#issuecomment-861891272 | https://api.github.com/repos/simonw/sqlite-utils/issues/272 | 861891272 | MDEyOklzc3VlQ29tbWVudDg2MTg5MTI3Mg== | 9599 | 2021-06-15T23:08:02Z | 2021-06-15T23:08:02Z | OWNER | `--csv -` should work though, for reading from stdin. The table can be called `stdin`. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
921878733 | |
https://github.com/simonw/sqlite-utils/issues/272#issuecomment-861891110 | https://api.github.com/repos/simonw/sqlite-utils/issues/272 | 861891110 | MDEyOklzc3VlQ29tbWVudDg2MTg5MTExMA== | 9599 | 2021-06-15T23:07:38Z | 2021-06-15T23:07:38Z | OWNER | `--csvt` seems unnecessary to me: if people want to load different CSV files with the same filename (but in different directories) they will get an error unless they rename the files first. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
921878733 | |
https://github.com/simonw/sqlite-utils/issues/272#issuecomment-861890689 | https://api.github.com/repos/simonw/sqlite-utils/issues/272 | 861890689 | MDEyOklzc3VlQ29tbWVudDg2MTg5MDY4OQ== | 9599 | 2021-06-15T23:06:37Z | 2021-06-15T23:06:37Z | OWNER | How about `--json` and `--nl` and `--tsv` too? Imitating the format options for `sqlite-utils insert`. And what happens if you provide a filename too? I'm tempted to say that the `--csv` stuff still gets loaded into an in-memory database but it's given a name and can then be joined against using SQLite `memory.blah` syntax. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
921878733 | |
https://github.com/simonw/sqlite-utils/issues/272#issuecomment-861889437 | https://api.github.com/repos/simonw/sqlite-utils/issues/272 | 861889437 | MDEyOklzc3VlQ29tbWVudDg2MTg4OTQzNw== | 9599 | 2021-06-15T23:03:26Z | 2021-06-15T23:03:26Z | OWNER | Maybe also support `--csvt` as an alternative option which takes two arguments: the CSV path and the name of the table that should be created from it (rather than auto-detecting from the filename). | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
921878733 |