Hi! On Wed, Aug 7, 2019 at 2:25 PM Markus Winand <markus.win...@winand.at> wrote: > I was playing around with JSON path quite a bit and might have found one case > where the current implementation doesn’t follow the standard. > > The functionality in question are the comparison operators except ==. They > use the database default collation rather then the standard-mandated "Unicode > codepoint collation” (SQL-2:2016 9.39 General Rule 12 c iii 2 D, last > sentence in first paragraph).
Thank you for pointing! Nikita is about to write a patch fixing that. > I also found two minor typos in the docs. Patch attached. Pushed, thanks. > -markus > ps.: I’ve created 230 test cases. Besides the WIP topic .datetime(), the > collation issue is the only one I found. Excellent work. Down to the > SQLSTATEs. For sure the most complete and correct SQL/JSON path > implementation I've seen. Thank you! ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
