2010-10-20, 15:22
xexe Wrote:Edit3: Special thanks to firnsy. Turns out my choice of UTF-8 char-set was the issue. Changed to Latin1 and the import is going strong. Were a few hours in now estimate perhaps 6 more.
Looks like I have the exact same problem as yourself. What was the SQL command to change to Latin1? I've changed it using the web tool but I am still getting the error.