Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

history_file directive ignored in ini #62

Open
thorstenkampe opened this issue Jul 15, 2019 · 2 comments
Open

history_file directive ignored in ini #62

thorstenkampe opened this issue Jul 15, 2019 · 2 comments

Comments

@thorstenkampe
Copy link

The history_file directive in the ini file is ignored. Litecli always writes to the default location.

@amjith
Copy link
Member

amjith commented Oct 25, 2019

There is no history_file directive in the ini file. It always writes to ~/.config/litecli/history.

I've tried to reduce this number of knobs of configure. Can you tell me what use case you're trying to address with this?

@thorstenkampe
Copy link
Author

thorstenkampe commented Oct 25, 2019

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:

  1. 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.
  2. 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.

Please feel free to close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants