Resolution: Not A Problem
Affects Version/s: 3.0.0
Fix Version/s: None
1) Let T be the TARGET and let V be the VALUE in an application of the Syntax Rules of this Subclause.
2) Let TD and SD be the declared types of T and V, respectively.
3) If TD is character string, binary string, numeric, boolean, datetime, interval, or a user-defined type, then
either SD shall be assignable to TD or there shall exist an appropriate user-defined cast function UDCF
from SD to TD.
NOTE 319 — “Appropriate user-defined cast function” is defined in Subclause 4.11, “Data conversions”
Implicit type conversion can occur in expressions, fetch operations, single row select operations, inserts, deletes,
and updates. Explicit type conversions can be specified by the use of the CAST operator.
The current implementation for ANSI store assignment is totally out of context.
According to this rule, `there shall exist an appropriate user-defined cast function UDCF`, the spark legacy store assignment is just fine because we do have appropriate cast functions.
At least according to the ansi cast rule, the current ANSI assignment policy is too strict to the ANSI cast rules