"Andrew Dunstan" <andrew@dunslane.net> writes:
> That's probably the worst of all possible options. Two very common uses of
> CSVlogs will be a) to load them into a PostgreSQL table and b) to load them into
> a spreadsheet such as Excel. In both cases having a Unix epoch time rather than
> a timestamp is likely to be very annoying.
Strangely those are precisely the use cases I was thinking of as well. For
both of those cases you need a timestamp which is unambiguous and understood
everywhere. Any text representation is going to depend on other tools using
the a compatible parser. Integers can be parsed by anything.
But perhaps I overestimate Excel's abilities.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
