Hi Sergei,
On Tue, May 31, 2016 at 06:48:31PM +0200, Sergei Golubchik wrote:
> Hi, Sergey,
>
> I think it's fine. I had a few questions though, see below:
Thanks for positive feedback. As I mentioned before, I'm less optimistic about
this patch due to many behavior changes. I can try to make a
Hi, Sergey,
I think it's fine. I had a few questions though, see below:
> commit 47aa5f9
> Author: Sergey Vojtovich
> Date: Fri May 6 13:44:07 2016 +0400
>
> MDEV-7660 - MySQL WL#6671 "Improve scalability by not using thr_lock.c
> locks
> for InnoDB
Hi, Vicențiu!
On May 29, Vicențiu Ciorbaru wrote:
> Hi Sergei!
>
> Can you please review the following patch for MariaDB 10.0. It fixes a
> compilation failure in Debian/Ubuntu when boost 1.60 or later is
> installed. I've looked into the code and checked if the #ifdef'ed
> code is used
On Tue, May 31, 2016 at 03:35:22PM +0400, Alexey Botchkov wrote:
..
> That JSON_CHECKER was produced by JSON.org itself, is really fast
> and nice. But it's not
> a parser - it just checks if the text makes the correct JSON.
> Well it took some time, but now ready. Now opening it for review.
So
Hi.
So i spent quite some time trying to get in use an existing JSON-parsing
libraries.
But surprisingly enough none seemed to be good enough.
Problems i met were like this:
1. Parsers are just slow.
- because they copy data - particularly key names and values.
- because they use
5 matches
Mail list logo