You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You are correct. Mycli and Litcli don't support that directive while pgcli and mssql-cli do. I'm using a single ini for all four dbcli applications so I got misled.
There were two use cases:
a single history file for all four dbcli shells I use. Since there are a few but significant syntax differences in the respective SQL dialects that turned out to be not useful.
a "portable" location for my history so I can take it with me an don't leave traces in the host (portable meaning on a USB thumb drive). That's less of an issue as it used to be.
The main issue is probably that I would wish that the dbcli shells would be more similar. From what I can see there are already two kinds of dbcli apps: the \n ones (pgcli and mssql-cli) and the \f ones (litecli and mycli). One uses named queries, the other one favorite queries, etc.
The
history_file
directive in the ini file is ignored. Litecli always writes to the default location.The text was updated successfully, but these errors were encountered: