search

stats4sd / Installation-Guides

A set of installation and basic use guides for software and tools used / recommended by the Research Methods Support / Stats4SD team
GNU General Public License v3.0
0 stars 0 forks source link

mysql blocks csv imports on latest versions #75

Closed chrismclarke closed 5 years ago

chrismclarke commented 5 years ago

https://stackoverflow.com/questions/52030767/how-to-solve-error-1148-from-mysql-workbench-and-not-cmd

https://bugs.mysql.com/bug.php?id=91872

Suggest we just link to version 5.7. What do you think @dave-mills?

chrismclarke commented 5 years ago

actually I had 8.0.13... will try latest 8.0.14

chrismclarke commented 5 years ago

Still not fixed, better thread of discussion here (lots of angry folk): https://bugs.mysql.com/bug.php?id=91891

chrismclarke commented 5 years ago

I spoke to shiphar and during the workshop we gave the 5.7 installers to everybody so I think we should change the mysql install guide to prompt users to install that version (until we can be assured the latest version works as desired)

dave-mills commented 5 years ago

I'm pretty sure this is solved if you make sure to tick the "legacy authentication" box when installing? (I remember there was a good reason I included that in the MySQL installation doc, but I can't remember exactly what that was!

I'll test it here quickly to see. Otherwise, we can go back to suggesting 5.7 as a nice, stable one.

dave-mills commented 5 years ago

Ok, ignore my previous comment - the legacy authentication thing is because clients like Heidi don't support the new sha-whatever authentication system yet.

The issue with the LOCAL INFILE command can be resolved in Heidi by selecting "Client parsed file contents" under Method.

I had a vague memory of giving advice on which method to use. Looking in our OneNote I've found a note mentioning "Client parses data" when importing a csv, so I think telling people to do that is in-line with what we recommended at the workshop (I think after some issue with the other method...)

Suggestion: I think ensuring that "client parses data" is set is fine, rather than suggesting people stick to an older version. I just checked the DB Forge importer too and that appears to avoid the LOCAL INFILE issue by default.

Screenshot 2019-01-24 13.43.37.png

chrismclarke commented 5 years ago

I tried that box and it still failed, have you tested it working correctly?

dave-mills commented 5 years ago

Hm. Yeah, it works fine for my little 2-column test. What data are you importing? Can I try with your db setup?

chrismclarke commented 5 years ago

The old setup is now dead as I reinstalled 5.7. I think let’s just hope things work given current advice and if not have a means people can contact us to raise issues.

dave-mills commented 5 years ago

Sure thing. I'll close this thread for now. If you happen to have seen the errors in the Heidi console that you were getting, we can re-open and I can try and recreate the issue here as I have a fresh new 8.14 install on Windows.