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

Restore-DbaDatabase quits prematurely when dbs exist #4949

Closed
potatoqualitee opened this issue Jan 14, 2019 · 4 comments · Fixed by #5064
Closed

Restore-DbaDatabase quits prematurely when dbs exist #4949

potatoqualitee opened this issue Jan 14, 2019 · 4 comments · Fixed by #5064
Assignees

Comments

@potatoqualitee
Copy link
Member

if i pipe in a number of databases, and the last one doesnt exist, but the first one does, restore-dbadatabase will quit instead of continuing on.

@Stuart-Moore
Copy link
Contributor

Gotten most of this done. However doing so makes AllowContinue pretty superfluous, are you happy to have the parameter dropped? or would you prefer me to leave it, but throw a warning that it's disappearing in 1.0 (or some other point)

@Stuart-Moore
Copy link
Contributor

@potatoqualitee are you happy for me to drop the param as mentioned above? It's ready to PR apart from that

@potatoqualitee
Copy link
Member Author

oh my so sorry, stuart. yes, please add the warning

@potatoqualitee
Copy link
Member Author

excellent ty! gonna do a release today

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

Successfully merging a pull request may close this issue.

2 participants