GHC 2019-01-12

2 comments.

, https://git.io/fhnCs in dbcli/litecli
Just want to chime in: most *nix command line tools are happy to create nonexistent files (or new direct subdirectories, if creating a directory structure is the tool's goal), but balk at the idea of creating intermediate subdirectories, unless explicitly told to do so. litecli is designed to deal with a single file at a time, so I don't think it's in the business of creating directories.

As a reference point, when you give `sqlite3` a non-existent path, it happily starts the shell; when you actually start making queries, it either creates the database file, or aborts with "unable to open database file" if the directory doesn't exist.

IMO it's okay for `litecli` to create the file immediately, but in the nonexistent directory case, a better error message saying so should be enough.

, https://git.io/fhnCG in dbcli/litecli
Feature request: support more parameter templates recognized by sqlite3_bind
============================================================================

Favorite queries seem to be very useful as poor man's prepared statements, which sqlite3 CLI lacks. However, right now only shell-style parameter templates `$1`, `$2`, etc. are allowed. It would be nice to support more templates recognized by [sqlite3_bind()](https://www.sqlite.org/c3ref/bind_blob.html), so that prepared statements can be directly taken from code or logs. At the very least, `?` would be immensely helpful.