Allow the user to import into a different database than the one specified in the file #1973
Conversation
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
Open
|
Could we use a simpler approach and just allow an optional |
|
Sorry, I missed your message. I wasn't aware of |
tobiasBora
force-pushed
the
allow_changing_name_during_import
branch
2 times, most recently
from
852e0ff
to
a09272a
Compare
tobiasBora
force-pushed
the
allow_changing_name_during_import
branch
from
a09272a
to
baea429
Compare
|
Ok, this one is tested (and fixed) now that I fixed my issue with #1995 (comment) Should be good to merge. |
|
Any update on this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix #1972 The callback allows a quite flexible solution as I can ask to the user a different name if the database already exists etc…