-
Notifications
You must be signed in to change notification settings - Fork 15
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
Import problems #3
Comments
One (or only) reason I see that is directly caused by the importer, could be new lines. The importer doesn't implement SQL spec, but buffers lines until it runs into a delimiter located at the end of a line. If a single (insert) statement spawns to multiple lines, you may get errors. Then there of course is query size limitations, and other server restrictions and security features, that apply to the importer. |
Yes I know, but I had in that moment not more time to debug this directly. I only try your tool and it throw that error. This week I will have more time to detect what exactly happen. |
The Was going to submit a pull request - but it looks like this has been fixed. Which makes me wonder what version I just pulled from packagist! |
@drewm would this cause slow downs during Export? Can you send link to your version of the fix and highlight how this has been fixed in the current master? |
In the case that a php variable is serialized in a field sometimes the import fails.
Currently I don't see why, I try to detect the problem, in the next days.
The text was updated successfully, but these errors were encountered: