The current data export script changes embedded new line characters to '\n'. the problem with this is that SQL clients tend not to change '\n' back to NL characters, and so the script cannot be used to recreate the database.
For example, if you have a text field with the contents (between ----)
----
\n
newline
----
It gets exported as '\n\nnewline'. This is obviously incorrect, since there is also no way to convert the exported data back to the original, since there is no way to determine whether the '\n' should be converted back to '\n' or NL.
This patch fixes the data export.
Patch to export new lines correctly
Patch has been accepted in a extended way: SQL-Preferences now allow to
choose the escape string