Force typing for Postgresql::date_trunc so it can be used in a condition

[florentdestremau]

I had the use case today to use date_trunc inside a query builder ->where statement and the lexer was lost because of an error like this:

An exception occurred while executing a query: SQLSTATE[42725]: Ambiguous function: 7 ERROR: function date_trunc(unknown, unknown) is not unique
LINE 1: ...pany_id = $1 AND DATE_TRUNC($2, p1_.created_at) = DATE_TRUNC...

This simple solution ensures postgresql knows what to expect.

[florentdestremau]

up @beberlei if you have time for this

[connorhu]

@florentdestremau Can you please make a rebase? Since your PR, a couple of CI checks have been included, it would be nice to see the results of those.

[florentdestremau]

I just rebased on master ! It seems like you need to approve the build run

[connorhu]

@derrabus Can you please approve the workflow? Thank you!

[derrabus]

Sure.

[florentdestremau]

I fixed the codestyle, the tests should all pass by now