I ran an additional test - created a table in MySQL with the VARCHAR column,
not JSON (as i did in MariaDB), and ran the same query.
So now MySQL had to parse the JSON and then look for path there.
--
MySQL [test]> select count(*) from jt2 where
Hi, Sergei.
I've requested your review on this, here are few additional notes.
I ran some benchmarks comparing against MySQL5.7's JSON field type. And
it seems
that the difference in performance is negligible.
For instance here are results for 20M rows with rather complicated JSON:
Space
2 matches
Mail list logo
