Ensure consistent sqlite output mode #140
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is another variation on #112. With a non-default output mode in .sqliterc output can have a format that the scripts don't handle. For instance, in my case I have
.mode column
in my .sqliterc. It turns out this meant that when setting up a new machine the output of the HISTDB_SESSION query was an all-whitespace string aligned to the column width (' '
) instead of the expected empty string, which meant that the output wasn't substituted with the default value0
.The fix here is to add
-list
to the sqlite3 CLI arguments everywhere that #112 modified. This is obviously unfortunate and there are probably other ways that .sqliterc can break things, but unless I'm missing it there's no way to turn the rc file off completely.