-
Notifications
You must be signed in to change notification settings - Fork 551
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
Support history_file configuration per dsn, and --history option. #1216
Open
laixintao
wants to merge
3
commits into
main
Choose a base branch
from
feature/history-config
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can support mapping of history file to not only DSN aliases, but database names as well. That way, if you have
mydb1
hosted on different servers, you could just configure:this could be useful to users that do not use DSN aliases.
There will be ambiguity if we do that: we'd have to figure out if
mydb1
is a DSN alias or a database name. We can look for matching DSN alias first, if user provided--dsn
when running the cli, and if there's no alias found, assume this is database name.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I like the idea that mapping of the history file for the database. I think it covers most of the use cases. Maybe consider
alias_dsn
is kind of overthinking and over-designed, I think we add too mush to configuration, and cloud leads to misunderstanding. I don't think users want to share history between databases. Even if they want to do that, they can use--histfile
option.Let's see, we only add a flag
sperate_history_on_database_name = False
, and add--histfile
option. (Also, if user use\c[onnect] database_name
, we should switch history file as well.If the user does want to share history between database, they can:
--histfile
, maybe use shell's alias together.named query
.What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that:
--histfile
to override the default history-file-per-database.prod
andbeta
database tables namedtable1_prod
,table2_prod
etc. Table structure was the same, but table names were different, so you could not use exactly the same query on those databases. This may be an edge case.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am convinced, I will only add a section named
dsn_history_file
section(maybe we cloud come up with a better name), and left other configs untouched.So the process of choosing a history file will look like this:
Do I understand it correctly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this looks exactly right.