On 07/13/2017 08:49 PM, Richard Hipp wrote:
The 3.20.0 release of SQLite is expected in about a week. Please report any issues that you have with the beta as soon as possible. Code is available in the "prerelease snapshot" at https://sqlite.org/download.html An overview of changes is at https://sqlite.org/draft/releaselog/3_20_0.html You can send issues to this email list, or directly to me.
https://sqlite.org/draft/releaselog/3_20_0.html says: * Added the "--newlines" option to the ".dump <https://sqlite.org/draft/cli.html#dump>" command to cause U+000a and U+000d characters to be output literally rather than escaped using the replace() <https://sqlite.org/draft/lang_corefunc.html#replace> function. This change is welcome, but quite strange. See my message (wishing it) http://mailinglists.sqlite.org/cgi-bin/mailman/private/sqlite-users/2017-July/073642.html and https://stackoverflow.com/questions/44989176/sqlite3-dump-inserts-replace-function-in-dump-change-from-3-18-to-3-19 What is strange is that according to the release log, that options only apply to .dump; I would expect that .mode insert also got an option similar to that, or perhaps a new .mode rawinsert (in both cases the effect would be that the INSERT statements generated would keep newlines and returns character verbatim). Why would there be a way to modify the output of newlines & returns character in dump but not in .mod insert outputs? Cheers. -- Basile STARYNKEVITCH == http://starynkevitch.net/Basile opinions are mine only - les opinions sont seulement miennes Bourg La Reine, France _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
