Specifying both starttime and endtime values crashes the arp API endpoint

[Morten Brekkevold]

If attempting to access the API endpoint `arp`, using both a starttime and an endtime value, causes an unhandled PostgreSQL error (NAV's "Ouch" page appears).

The PostgreSQL error looks like this:

ERROR: function pg_catalog.overlaps(timestamp without time zone, timestamp without time zone, unknown, unknown) is not unique at character 59
HINT: Could not choose a best candidate function. You might need to add explicit type casts.

Using both starttime and endtime values produces a query using the PostgreSQL OVERLAPS keyword, but since the timestamps are given as strings, PostgreSQL is having trouble choosing the correct typecasting function to fit with the OVERLAPS keyword.

The strings should explicitly be cast to timestamps to avoid this issue.

[Morten Brekkevold (mbrekkevold)]

fix here: https://nav.uninett.no/hg/nav/rev/901e4f1a83f0