Timeline for Import CSV to MySQL with long text fields containing line breaks
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 23, 2019 at 12:55 | history | edited | James | CC BY-SA 4.0 |
exclude dead link
|
| Nov 26, 2018 at 14:47 | vote | accept | James | ||
| Nov 25, 2018 at 19:47 | answer | added | Rob Gravelle | timeline score: 2 | |
| S Mar 8, 2018 at 17:53 | history | suggested | Danny_ds | CC BY-SA 3.0 |
Improved title
|
| Mar 8, 2018 at 16:30 | review | Suggested edits | |||
| S Mar 8, 2018 at 17:53 | |||||
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Aug 10, 2015 at 12:13 | comment | added | Rick James |
Try LINES TERMINATED BY '' or LINES TERMINATED BY ';'; I suspect that leaving out the clause defaults it to LINES TERMINATED BY '\n'. Suggest you experiment.
|
|
| Aug 10, 2015 at 11:58 | comment | added | James |
@RickJames. Please, correct me if I wrong, but I think that with a three-column table and a CSV separated by ';', the LOAD must take a new line every three fields, right? Actually, I don't know how LOAD works, but I imagine it to be so.
|
|
| Aug 9, 2015 at 22:00 | comment | added | Rick James |
How is LOAD supposed to know when each "line" is finished?
|
|
| Aug 7, 2015 at 19:54 | history | asked | James | CC BY-SA 3.0 |