On 2017-11-02 20:51:23 +0000, Rhhh Lin wrote:
[...]
> where timestamp BETWEEN 1506676560000 AND 1508750220000
[...]
> *Also, as a sidenote - can someone please expand on why one (I was not involved
> in the creation of this DB/schema definition) would choose to have the
> definition of the timestamp column as a bigint in this case?
The numbers look like Java timestamps (Milliseconds since the epoch). So
probably the programs accessing the database are written in Java and the
programmer decided that it's simpler to do all timestamp computations in
Java than in SQL. Or maybe the programmer just felt more comfortable
with Java-like timestamps than with calendar dates. (I have done the
same (with Unix timestamps, i.e. seconds since the epoch). Although in
the cases where I've done it I had the additional excuse that the
database didn't support timestamps with timezones, which isn't the case
for PostgreSQL.)
hp
-- _ | Peter J. Holzer | we build much bigger, better disasters now
|_|_) | | because we have much more sophisticated
| | | hjp@hjp.at | management tools.
__/ | http://www.hjp.at/ | -- Ross Anderson <https://www.edge.org/>
