[Wranglers] Help Oracle Query optimizer by avoiding Implicit Type Conversion in JSON Access

Ali, Saqib docbook.xml at gmail.com
Wed Feb 12 02:26:03 UTC 2025


An excellent blogpost by Philipp Salvisberg on why implicit type conversion
should be avoided in Oracle especially when working with JSON data:
https://www.salvis.com/blog/2025/01/28/avoid-implicit-type-conversion-in-json-access/

Always use a SQL/JSON path expression method (binary(), boolean(), date(),
dateWithTime(), number(), string(), …) when comparing a JSON value to a
non-JSON value in SQL. This way you avoid implicit type conversions,
improve the readability of your code, and give the Oracle Database
everything it needs to create an optimal execution plan.

I wonder if this is applicable in the Snowflake world as well. Snowflake
performs a lot of implicit casting and I have wondered if this implicit
casting slows down the join when used in the join condition.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://analyticsengineering.net/pipermail/wranglers/attachments/20250211/c9e55cc0/attachment.htm>


More information about the Wranglers mailing list