"Minimum" aggregation function returns null even if non-null values are present. This is not the behaviour of SLQ, that returns the minimum of non-null values if any. it is a severe problem because if I have several columns of wich i need to calcumate the minimum, but each of them contains null values, I cannot use "first non null values", because ordering on field would cause erroneous results for the other fields. Same problem with filtering: filtering values for one field would cause possible loss of data for other fields.
Since SQL behaviour is different I think this should be fixed. But I guess also another function (e.g. "Minimum (not null)") can be implemented.