Quick fix for restore of backups made by dump fails silently #402
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.
When I use the restore command to restore previously backup made by dump, it seems everything works fine (no errors). But when I check the restored database it's only restored up to the first table with a big amount of rows. The dump is fine, because I can restore it succesfully with for example MySQL Workbench.
Found that the used scanner in databse restore package has a default buffer which has a maximum content which is too small for the long lines generated by dump. A possible work-around is to supply dump with maxAllowedPacket option with the max size of this default buffer.
Or supply the scanner with a buffer which can handle the long lines, like I did in this pull request.