I'm trying to import into mySQL a text file containing memos. I don't know how they managed to do this, but while the memo field is consistently terminated by CR LF, parts of the text itself contains a mixture of CR, LF, and CR LF line breaks as well.
Naturally this breaks my ability to import it, as there is no clear indication of what constitutes a line break. Roughly half the data is lost during import, and 25% of what made the cut ends up truncated.
Is there any feasible way of sorting this mess out? It was originally exported from Access.
Thanks!

The last line was a recent addition in an effort to try to solve this import problem. The original problem as well was that a memo might get imported up until a line break, I assume mySQL thinks it's the start of the next line so it dumps the rest of the text because it's not valid CSV and then goes to the next line, which sometimes doesn't work just the same.
– Ivan Aug 27 '13 at 13:05