Thanks! I can make do with replace() for now (as in my particular case, I only have CRLF & TAB to replace)
On Thu, Feb 4, 2016 at 11:39 AM, Richard Hipp <drh at sqlite.org> wrote: > On 2/4/16, Richard Hipp <drh at sqlite.org> wrote: > > On 2/4/16, Eric Grange <zarglu at gmail.com> wrote: > >> Hello, > >> > >> I have been experimenting with using the json1 extension to generate > json > >> sql-side rather than code-side, but I am hitting an issue with the CR & > >> LF > >> characters which are not escaped, which results in json that fails > >> JSON.parse or use as JSONP in browsers. Ideally CR / LF should be > encoded > >> as \r and \n respectively. > >> > >> Is it by design or an oversight? > > > > Oversight. https://www.sqlite.org/src/tktview/ad2559db380a > > > > Now fixed on trunk. Snapshot available at https://www.sqlite.org/ > and the change is mentioned on the draft change log for the next > release at https://www.sqlite.org/draft/releaselog/3_11_0.html > > -- > D. Richard Hipp > drh at sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
