RE: TZ in Odoo

I believe with this, the best solution is to have all dates and times within the DB be in UTC.

It’s only when presented to the user that a TZ should then be attached to the dates and times.

Timezones are too confusing otherwise… what happens if the DB ends up in a timezone which has daylight saving time? If the DB has a datetime which is the daylight saving shift, what should the other non-DST people interpret the time as? For us here in Australia, on one day of the year there is no 2am (it skips from 1:59am through to 3:00am), another day of the year we get two sets of 2:59am (it skips back to 2:00am at 3:00am that day).

I’m not sure if this has been cleanly implemented through-out the Odoo database however (I suspect not)

I believe DB in UTC would respect your use cases. For standard usage the view interface would convert from UTC to localtime.

Then for a particular situation where you care about an alternative TZ (like your Fiji example) it would be possible to view things in this TZ (entry and display would be converted here).

Things like calendar appointments could even be shown as multiple timezones (so that you can plan a meeting time which is suitable for multiple people in different timezones), just by applying the appropriate offsets from the UTC that the DB will record everything as.