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/datasette/issues/1382#issuecomment-864480051 | https://api.github.com/repos/simonw/datasette/issues/1382 | 864480051 | MDEyOklzc3VlQ29tbWVudDg2NDQ4MDA1MQ== | 9599 | 2021-06-20T00:20:06Z | 2021-06-20T00:21:02Z | OWNER | Yes you can - thanks for pointing this out, I've added a comment to the `install.sh` script in the `datasette-csvs` Glitch project: ```bash pip3 install -U --no-cache-dir -r requirements.txt --user && \ mkdir -p .data && \ rm .data/data.db || true && \ for f in *.csv do # Add --encoding=latin-1 to the following if your CSVs use a different encoding: sqlite-utils insert .data/data.db ${f%.*} $f --csv done ``` So if you edit that file in your own project and change the line to this: sqlite-utils insert .data/data.db ${f%.*} $f --csv --encoding=iso-8859-1 It should fix this for you. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 925406964 | |
https://github.com/simonw/sqlite-utils/issues/286#issuecomment-864594956 | https://api.github.com/repos/simonw/sqlite-utils/issues/286 | 864594956 | MDEyOklzc3VlQ29tbWVudDg2NDU5NDk1Ng== | 9599 | 2021-06-20T18:38:05Z | 2021-06-20T18:38:05Z | OWNER | 3.10 is out in Homebrew now (they turn that around so fast): https://formulae.brew.sh/formula/sqlite-utils | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 925487946 | |
https://github.com/simonw/sqlite-utils/issues/289#issuecomment-864609271 | https://api.github.com/repos/simonw/sqlite-utils/issues/289 | 864609271 | MDEyOklzc3VlQ29tbWVudDg2NDYwOTI3MQ== | 9599 | 2021-06-20T20:42:07Z | 2021-06-20T20:42:07Z | OWNER | Wow, thank you! I didn't know about `typing.cast()`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 925677191 | |
https://github.com/simonw/sqlite-utils/issues/278#issuecomment-864621099 | https://api.github.com/repos/simonw/sqlite-utils/issues/278 | 864621099 | MDEyOklzc3VlQ29tbWVudDg2NDYyMTA5OQ== | 601708 | 2021-06-20T22:39:57Z | 2021-06-20T22:39:57Z | CONTRIBUTOR | Fair. I looked into it, it looks like it could be done, but it would be _a bit ugly_. I can upload and link a gist of my exploration. **Click** can parse a first argument while still recognizing it as a sub-command keyword. From there, the program could: 1. ignore it preemptively if it matches a sub-command 2. and/or check if a (db) file exists at the path. It would then also need to set a shared db argument variable. Click also makes it easy to parse arguments from environment variables. If you're amenable, I may submit a patch for only that, which would update each sub-command to check for a DB/SQLITE_UTILS_DB environment variable. The goal would be usage that looks like: `DB=./convenient.db sqlite-utils [operation] [args]` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 923697888 |