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

[pnorman]

> That said, if you are dead sure that all osm clients know that they are geting UTC from the db and do the conversion-before-printing work themselves, you can keep using 'without timezone'. But for such a distributed project as osm, it's probably better to play it safe

Well, we know that some parts of the OSM stack get it wrong because we've already got an osmosis bug about the matter. 

OSM data has a time zone associated with it, it just happens to all be the same.

I don't feel this is actually a substantial change as it shouldn't require changes for anything which currently is behaving correctly.

@vincentdephily How'd you hack around client bugs? That might work for me in the short term for getting around the data loading bugs

---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/375#issuecomment-21335589
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20130722/70789fb6/attachment-0001.html>