maria-developers team mailing list archive

[Sergey Petrunia <sergey@xxxxxxxxxxx>]

One more thing:

On Mon, Sep 14, 2020 at 03:38:38PM +0400, Alexey Botchkov wrote:
> CREATE TABLE t1(id INT, f1 JSON);
> INSERT INTO t1 VALUES (1, '{\"1\": 1}'), (2, '{\"1\": 2}'), (3, '{\"1\":
> 3}'),
> (4, '{\"1\": 4}'), (5, '{\"1\": 5}'), (6, '{\"1\": 6}');
> 
> SELECT * FROM t1 WHERE id IN
>   (SELECT id FROM t1 as tt2,
>       JSON_TABLE(f1, "$" COLUMNS (jf FOR ORDINALITY)) AS tbl);

I've noticed that Optimizer Trace is not saved for this query. I get

MariaDB [test]> select * from information_schema.optimizer_trace\G
*************************** 1. row ***************************
                            QUERY: 
                            TRACE: 
MISSING_BYTES_BEYOND_MAX_MEM_SIZE: 0
          INSUFFICIENT_PRIVILEGES: 1
1 row in set (0.001 sec)

INSUFFICIENT_PRIVILEGES: 1!

This is only supposed to happen when the query uses VIEWs which definition
cannot be viewed by the user executing the query.  

Could you investigate and fix this please?

BR
 Sergei
-- 
Sergei Petrunia, Software Developer
MariaDB Corporation | Skype: sergefp | Blog: http://s.petrunia.net/blog