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/476#issuecomment-1229370823 | https://api.github.com/repos/simonw/sqlite-utils/issues/476 | 1229370823 | IC_kwDOCGYnMM5JRrXH | 9599 | 2022-08-28T04:07:15Z | 2022-08-28T04:07:15Z | OWNER | https://sqlite-utils.datasette.io/en/stable/changelog.html#v3-29 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 1353196970 | |
https://github.com/simonw/sqlite-utils/issues/471#issuecomment-1229430228 | https://api.github.com/repos/simonw/sqlite-utils/issues/471 | 1229430228 | IC_kwDOCGYnMM5JR53U | 4312421 | 2022-08-28T10:43:35Z | 2022-08-28T10:43:35Z | NONE | Is it still nfortunately slow and tricky when playing with floats ? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 1352932716 | |
https://github.com/simonw/sqlite-utils/issues/420#issuecomment-1229438242 | https://api.github.com/repos/simonw/sqlite-utils/issues/420 | 1229438242 | IC_kwDOCGYnMM5JR70i | 9599 | 2022-08-28T11:34:21Z | 2022-08-28T11:34:37Z | OWNER | I found a fix that makes that `global` workaround unnecessary: - #472 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 1178546862 | |
https://github.com/simonw/sqlite-utils/issues/474#issuecomment-1229449018 | https://api.github.com/repos/simonw/sqlite-utils/issues/474 | 1229449018 | IC_kwDOCGYnMM5JR-c6 | 14294 | 2022-08-28T12:40:13Z | 2022-08-28T12:40:13Z | NONE | Creating the table before inserting is a useful workaround, thanks. It does require figuring out the `create table` syntax and listing all the fields manually, though, which loses some of the magic of sqlite-utils. I was expecting to find an option like `--headers=foo,bar` (or `--header-row='foo\tbar'`, if that would be easier) - not necessarily that exact syntax, but something that would essentially be treated the same as having a header row in the file. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 1353074021 | |
https://github.com/simonw/sqlite-utils/issues/478#issuecomment-1229563718 | https://api.github.com/repos/simonw/sqlite-utils/issues/478 | 1229563718 | IC_kwDOCGYnMM5JSadG | 9599 | 2022-08-28T22:07:03Z | 2022-08-28T22:07:03Z | OWNER | What should happen if you run this: sqlite-utils tables data.db bad_table Where `bad_table` is a table that does not exist? I think it should error rather than failing silently. That way you can use the error code to confirm that a list of expected tables exist. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 1353481513 |