-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
Add postgresql schema support #424
Conversation
Since this appears to not be ready for review, I am marking this PR as draft. Please mark it as "Not Draft" when lint/tests are passing |
Great feature. Looking forward to it! |
@twkrol Are you still planning to work this PR? |
Yeah, I want to. Just got some busy days recently. |
Hi @twkrol @Archmonger, What is the status of this PR? Why is the status in the draft? |
Hey, I would love to merge this feature, but need help to make tests. Anyone? |
@angryfoxx Tests are still needed for this PR. On top of that, there's a more pressing issue that blocks all PRs from being merged #483 |
Hi again @Archmonger, is that issue still persisting? I can write test and update this pr if there is no blocker. |
Yes. @johnthagen has created a workaround for our broken workflows. PRs are now mergeable again. |
@angryfoxx Please resolve merge conflicts and merge |
Hi again guys @Archmonger @johnthagen. I have created pr about that issue and could you review it ? |
Closing this in favor of #507 |
Type of PR (feature, enhancement, bug fix, etc.)
Feature
Description
Added '-n' for specyfing schema to backup/restore
Why should this be added
Usefull for multitenant applications where customer's data are separated by schema, so one can backup/restore selected schema only
Checklist