# Json\_table columns parsing suggestions

**URL:** <https://forums.toadworld.com/t/json-table-columns-parsing-suggestions/61711>\
**Category:** Toad for Oracle - Beta\
**Created:** [June 8, 2026, 12:56pm UTC](https://forums.toadworld.com/t/json-table-columns-parsing-suggestions/61711 "2026-06-08T12:56:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dolo](https://avatars.discourse-cdn.com/v4/letter/d/9e8a1a/32.png) [@dolo](https://forums.toadworld.com/u/dolo)\
**Post date:** [June 8, 2026, 12:56pm UTC](https://forums.toadworld.com/t/json-table-columns-parsing-suggestions/61711/1 "2026-06-08T12:56:19Z")

</div>

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.

 ![image](https://global.discourse-cdn.com/quest/original/3X/2/d/2d4058d50b098db9a5a0a3b691b87e0dacd3d142.png)

 ![image](https://global.discourse-cdn.com/quest/original/3X/8/8/88465e2c663dba9fc1c33b14c579b9ca562cbf78.png)

---

<div class="post-metadata">

**Author:** ![JohnDorlon](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/johndorlon/32/9997_2.png) [@JohnDorlon](https://forums.toadworld.com/u/JohnDorlon)\
**Post date:** [June 8, 2026, 1:18pm UTC](https://forums.toadworld.com/t/json-table-columns-parsing-suggestions/61711/2 "2026-06-08T13:18:29Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![dolo](https://avatars.discourse-cdn.com/v4/letter/d/9e8a1a/32.png) [@dolo](https://forums.toadworld.com/u/dolo)\
**Post date:** [July 23, 2026, 12:54pm UTC](https://forums.toadworld.com/t/json-table-columns-parsing-suggestions/61711/3 "2026-07-23T12:54:05Z")

</div>

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;`

---

<div class="post-metadata">

**Author:** ![milos.lekovic](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@milos.lekovic](https://forums.toadworld.com/u/milos.lekovic)\
**Post date:** [July 27, 2026, 5:49am UTC](https://forums.toadworld.com/t/json-table-columns-parsing-suggestions/61711/4 "2026-07-27T05:49:00Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![brandon](https://avatars.discourse-cdn.com/v4/letter/b/f08c70/32.png) [@brandon](https://forums.toadworld.com/u/brandon)\
**Post date:** [October 7, 2026, 9:04pm UTC](https://forums.toadworld.com/t/json-table-columns-parsing-suggestions/61711/5 "2026-10-07T21:04:59Z")

</div>

Good afternoon.

Toad for Oracle Base Edition (64-bit) 26.2.272.9090 still considers the 'PRETTY' keyword an error.

Thanks for taking a look!