Such declarations are currently rejected by FunctionDef.parse() because of the array type reference, so such UDFs are treated as unknown. I appreciate that VOLLT does not support arrays at present (see #138) and also that ADQL does not define any syntax for array declaration. However it would be nice (for me) if such declarations could be parsed and marked supported in the FeatureSet, even if the parameter type or return type is not understood. Then at least the names and parameter counts of such UDFs could be validated in ADQL submitted to the ADQLParser.
I can imagine that in absence of proper array support, such a change might be either (a) very easy or (b) very difficult. If (b), no problem! But if (a) maybe you could consider it.
DaCHS declares some UDFs with parameter or return values of array type, e.g.:
Such declarations are currently rejected by
FunctionDef.parse()because of the array type reference, so such UDFs are treated as unknown. I appreciate that VOLLT does not support arrays at present (see #138) and also that ADQL does not define any syntax for array declaration. However it would be nice (for me) if such declarations could be parsed and marked supported in the FeatureSet, even if the parameter type or return type is not understood. Then at least the names and parameter counts of such UDFs could be validated in ADQL submitted to the ADQLParser.I can imagine that in absence of proper array support, such a change might be either (a) very easy or (b) very difficult. If (b), no problem! But if (a) maybe you could consider it.