Json_table columns parsing suggestions

[dolo]

Toad does not seem to detect or parse json_table columns that have both on empty and on error specifiers together, for example first coumn on below code.
Also second colum there is other case where the default value 123456 is underlined red as Toad expects string, not number. So two red exclamation icons here:

select * from json_table('{"s": "test"}' format json, '$'
columns (
s varchar2 path '$.s' NULL on empty error on error
, n number path '$.n' default 123456 on empty error on error
));

Scirpt itself works fine as F5/F9 execution or in package code.

[JohnDorlon]

Thanks, I'll report it to our parser team.

[dolo]

Seems to be nice in beta, found only one more similar case with negative numbers:

select * from json_table('{"s": "test"}' format json, '$'
columns (
n number path '$.n' default -123456 on empty error on error
));

Edit: one more where the "pretty" keyword is not accepted in parsing:

select json_object(
's' value 'test'
absent on null
pretty
)
from dual;

[milos.lekovic]

Hey, we'll work on this and it should be fixed in the next iteration.