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 value 0.
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.
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 columnin 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
-listto 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.