[openstreetmap-website] Switch to TIMESTAMP WITH TIME ZONE for current_* tables (#375)

pnorman notifications at github.com
Mon Jul 22 01:05:42 UTC 2013


Currently the current_nodes, current_ways and current_relations tables include a timestamp column of type ``TIMESTAMP WITHOUT TIME ZONE``.

I've asked around and consulted some sources and the advice I got was best summarized as

```19:12 <RhodiumToad> pnorman: unless you're writing a calendaring/scheduling app, timestamp with time zone is pretty much always the way to go```

This is not purely a theoretical concern. Currently there is no way to my knowledge to load to an apidb that does not result in time zone errors. See [this osmosis discussion](http://lists.openstreetmap.org/pipermail/osmosis-dev/2013-July/001586.html)

Neither the rails port nor cgimap returns the correct timestamps right now on any instance other than osm.org running on a server where the local time is not set to UTC, because the problem is in the database.

Cross-reference pnorman/openstreetmap-api-testsuite#1
cc: @brettch, @zerebubuth, @iandees

---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/375
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20130721/3dcdbaae/attachment.html>


More information about the rails-dev mailing list