-
Notifications
You must be signed in to change notification settings - Fork 146
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
saved connection details #386
Comments
I like the analogy with ssh config. I think it should be read-only (i.e. sqlline reads from the file if present but never writes to it). Writing might accidentally store passwords that users do not wish to store, in files that are not secure enough. Like |
@julianhyde an alternative for the password could be to use a separate config for password. the password could be encrypted using something like jasypt. |
True. I'm wary of using (two way) encryption (because you have to store the decrypt key somewhere). Better let people store their passwords in files that only they can see (and only they edit, but we read). |
Certainly — yes — having something like a |
I also have something in my sandbox e.g. there is a branch https://github.com/snuyanzin/sqlline/tree/saved_connections_in_file
where
example of such file
|
There should be a way to save/load the connections to a file. This helps in quickly connecting to a previous connection.
This is somewhat similar to the ssh config and will open up possibilities to have the different auto-commit, transaction-isolation, readOnly for each connections in future.
The current properties format may prove inadequate for this, and a new format like TOML or YAML may need to be agreed upon (I'm leaning towards the former).
The text was updated successfully, but these errors were encountered: