This just adds explicit forwarding of the generic Result parameter of the two QueryBuilder.aggregate() variants which weren't doing so already. It was already being implicitly forwarded due to type inference, but better to do so explicitly.
Also adds notes to the sum() and average() sets of methods warning that the Field.Value return types are not always correct (usually only causes problems with Postgres) and giving the workaround. This is related to #379 and vapor/fluent-postgres-driver#166 but does NOT fix those issues; it only clarifies one of the ways to get around the problem.
This just adds explicit forwarding of the generic
Result
parameter of the twoQueryBuilder.aggregate()
variants which weren't doing so already. It was already being implicitly forwarded due to type inference, but better to do so explicitly.Also adds notes to the
sum()
andaverage()
sets of methods warning that theField.Value
return types are not always correct (usually only causes problems with Postgres) and giving the workaround. This is related to #379 and vapor/fluent-postgres-driver#166 but does NOT fix those issues; it only clarifies one of the ways to get around the problem.