> On 11/10/19, Richard Hipp <[email protected]> wrote:
> > It seems there are also problems in generating valid JSON for large
> > unicode characters. For example:
> >
> > SELECT json_quote(char(1114111));
> >
> > I'm working on the problem....
> I take that back. It seems that the spec allow arbitrary UTF-8
> characters in a JSON string, without the need to escape them using
> the backslash notation, except for ", \, and control characters, and
> so the current behavior is correct after all, as far as I can tell.
> Please let me know if you see any cases that I have mised that do
> not work.
It seems that it is time to remind everybody about
https://github.com/nst/JSONTestSuite
and the adjunct article
http://seriot.ch/parsing_json.php
Actually, the github repository is considered to be an appendix to the
article.
Might be interesting to submit the sqlite json parser to this
testsuite for comparison.
--
See you,
Andreas Kupries <[email protected]>
<https://core.tcl-lang.org/akupries/>
Developer @ SUSE Software Canada ULC
<[email protected]>
Tcl'2019, Nov 5-8, Houston, TX, USA. http://www.tcl.tk/community/tcl2019/
-------------------------------------------------------------------------------
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
