price.date, transaction.post_date and neutral time

When exporting data from SQL backends, I see some inconsistencies in the handling of some date & datetime columns. In the prices table, when adding price via the price editor, I see in the date column a datetime with the UTC of the /MM/DD 00:00:00 of my local timezone (CET). For instance, for

Re: price.date, transaction.post_date and neutral time

> On Feb 11, 2018, at 4:33 AM, Sébastien de Menten wrote: > > When exporting data from SQL backends, I see some inconsistencies in the > handling of some date & datetime columns. > > In the prices table, when adding price via the price editor, I see in the > date column a

Re: price.date, transaction.post_date and neutral time

Yes definitely not a top priority if it works and the change is costly and delicate. Regarding prices.date not being handled in neutral time, is there some difference with transactions.post_date regarding it's behavior/type or should it also use neutral time? On Feb 11, 2018 16:53, "John Ralls"

Re: price.date, transaction.post_date and neutral time

The reason post_date is (as of 2.6.12) treated specially is that people expect to change timezones and have the displayed posted date for a transaction not change on them. Prices in general have a specific date-time associated with them, particularly if the market on which the security trades