Add a strategy where if a function has ordinary function syntax and we don't recognize it we assume that it can take any argument types and returns a result of unknown type.
We will still need to change the parser to handle functions with non-standard syntax (e.g. DATEADD). And it's a good idea to explicitly add commonly used non-standard functions (e.g. MD5, CONCAT).”
[19/Sept/2019] Functions have to have ordinary function syntax [e.g. foo(arg0, ...)]. Current implementation idea is to:
- Create a known/unknown flag for use within the validator
- Create a more permissive SqlUnresolvedFunction to be passed through validator
- Allow OperandTypes to be variadic