We have a very similar problem. We keep timestamps in numeric form as "epoch nanos" (nanoseconds from 1970-01-01 00:00) We are using PostgreSQL as the database, and I would very much like to use the native type (TIMESTAMP) [1], but PostgreSQL only keeps TIMESTAMP columns to microseconds, not nanoseconds. :-(
Using the native DBMS types allows use of native DBMS time and interval functionality, unless you like doing it yourself.
we have some tables where we have timestamp and other places we have millis. We are also using postgreSQL database.
I have asked this question so that I can know whether any other person faces problem like this, it is kind of annoying when I see different ways of storing the time, but not knowing what is the best practise to save time in database.
I have asked this question so that I can know whether any other person faces problem like this, it is kind of annoying when I see different ways of storing the time, but not knowing what is the best practise to save time in database.