In this Topic:
Integers and Doubles¶
Uint8Array object, it is converted into a Snowflake SQL binary value.
- All precision beyond milliseconds is lost.
Dategenerated from SQL TIMESTAMP_NTZ no longer acts as “wallclock” time; it is influenced by daylight saving. This is similar to behavior when converting TIMESTAMP_NTZ to TIMESTAMP_LTZ.
Dategenerated from SQL TIMESTAMP_TZ loses time zone information, but represents the same moment in time as the input (similar to when converting TIMESTAMP_TZ to TIMESTAMP_LTZ).
Daterepresenting midnight of the current day in the local time zone.
Dateobjects are converted to the UDF’s result data type, adhering to the same conversion semantics as casts from TIMESTAMP_LTZ(3) to the return data type.
Dateobjects nested inside VARIANT objects are always of type TIMESTAMP_LTZ(3).
Variant, Objects, and Arrays¶
$, while subsequent characters can be alphanumeric,
The following three examples illustrate UDFs that use arguments referenced by name:
Null and Undefined Values¶
undefined value in addition to null.
Excessive stack depth due to recursion will result in an error.
You should not rely on global data being available between function calls from one row to the next. The global state may be erased between UDF calls to distinct rows. It is safe to use global state within a UDF.
eval() function is disabled.
Returned Variant Size and Depth¶
Returned variant objects are subject to size and nesting-depth limitations. Should any object be too large or too deep, you will receive an error:
|Size:||Currently limited to several megabytes, but subject to change.|
|Depth:||Currently limited to a nesting depth of 1000, but subject to change.|