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.

Sign up for GitHub

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

Jump to bottom

Allow the user to import into a different database than the one specified in the file #1973

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Allow the user to import into a different database than the one specified in the file #1973

wants to merge 1 commit into from

Conversation

tobiasBora
Copy link
Contributor

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…

@tobiasBora tobiasBora mentioned this pull request Apr 29, 2024
Open
@dfahlander
Copy link
Collaborator

Could we use a simpler approach and just allow an optional name property? I suppose letting the name depend on the other info from the file is less common use case but when that is needed, one could use peakImportFile() to get that information beforehand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Import a database with a different name
2 participants
@tobiasBora @dfahlander