Add an option to truncate timestamps to integers. about pgsql

[devinus]

Is it because Postgres supports larger time ranges?

[pguyot]

It is because PostgreSQL supports more precision in timestamps. As Erlang preserves order between floats and integers, such timestamps can be compared with timestamps(). For example, the following holds:

true = {{{2013,3,21},{18,35,0.241573}}} < {{{2013,3,21},{18,35,1}}},
true = {{{2013,3,21},{18,35,0}}} < {{{2013,3,21},{18,35,0.241573}}}.

There could be an option to truncate timestamps to integers.

[devinus]

@pguyot That would probably help. It was a thorn in our side when we used epgsql too.

[benmmurphy]

It would be nice to have an option to always return a float as the second value as well. Having it be either an int() or a float() depending on the number of micro seconds can hide some bugs.

[pguyot]

The option is {datetime_float_seconds, round | always | as_available}. as_available is the default, returning integer timestamps when the number of microseconds is 0.