Anse, one of the fields in my SQL file is a MEDIUMTEXT field, and has conversational sentences that contain double quotes as part of human conversations.
So if I do a general search and replace of double quotes for back ticks, that will create all the double quotes as conversation within the MEDIUMTEXT field to get converted too.
Would that cause the import to fail?
I did a small test and it looks like it will still import correctly, just that the conversation threads will look like they have back ticks instead of double quotes in them.
Small Issue #2
Also, I noticed that any of these conditional commands seem to muck up the import too:
/*!40000 ALTER TABLE "post" DISABLE KEYS;*/
It only works when I delete all of them. Any way around that too? Should I just delete them or is there a way to keep them in there.