When using a logger table, all documentation seems to specify that a date-time needs to be implemented using UTC time.
Or is this only related to partitioning date-time column?
How can we show the local date-time to make it nicer for our users so they can see DB entries in their local time?
- Can we add another date-time column, but with a local date-time and not the UTC?
Or will this interfere with the partitioning date-time column? - Should we add a numeric date-time column that stores the local date-time using the DateTime.ToOADate()?
- Is there another approach?
Hi Brecht,
You could indeed add a second datetime column. There are connectors with both a start- and end-time. Just don't add the <Partition> tag to the extra columns, so that they indeed don't interfere with the partitioning.
Adding a 'double' column is also an option, in combination with ToOADate(), and will certainly not interfere with the partitioning.
Depending on how the data will be visualised (element in Cube, dashboard, low code app, ...) it could also be an option to do the conversion on the client itself.