Comment 3 for bug 1255612

Revision history for this message
Martin Collins (mkc-steadfast) wrote :

Holger, your fix only affects datetimes with no time, but those *with* time are also not converted to UTC in search domains.
Also, context_timestamp() converts from UTC to the client's tz, which is the wrong way round.

I attach my attempt at fixing both issues. It will affect any datetime on the right of a domain that is parsed by this code. I would hope that any which are already in UTC will have 'UTC' in their tz or have no tz in their context (can anyone confirm this?) so will not be converted.

For 6.1 only. (Something worrying has happened in 8)