Restore using the mysql binary to prevent memory errors. #20
Conversation
This file contains hidden or 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
|
hey @dcblogdev -- i know you must be pretty busy but could you maybe have a look at this ?:) |
|
I'm away with work at the moment, I'll be able to look at this next week, thanks for raising it |
|
Hey @dcblogdev i was wondering why this is still open. Is there an issue with it? Is there something wrong with it? I'm not trying to be pushy, just trying to understand why this hasn't been merged as it's been a while since it has been created.. |
|
my apologies, I will get to this today. |
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.
Modify the restore process, so that it uses mysql instead to prevent memory issues.
This should close #18 and simplify the restore process, along with increasing the speed of the restore.