[OSM-dev] OSM Date Formats

Robert Hart bathterror at gmail.com
Sun Sep 30 11:26:47 BST 2007


On 30/09/2007, Brett Henderson <brett at bretth.com> wrote:
> Robert Hart wrote:
> > On 29/09/2007, Brett Henderson <brett at bretth.com> wrote:
> >
> >> I'd like to standardise on a UTC date with Z suffix similar to the
> >> osmosis example.  I am willing to remove the millisecond information to
> >> make it even shorter if necessary (I'll have to write my own formatter
> >> but not a big job).  As a nice side effect this would noticeably reduce
> >> the size of the planet.
> >>
> >
> > To be honest I'm really surprised that a timestamp is passing from the
> > client through the server into the database without being parsed at
> > all. Surely a) a proper timestamp format can and should be used in the
> > db. and b) we shouldn't necessarily be trusting the time as determined
> > by the client anyway.
> >
> > Rob
> >
>
> Um, I think we're talking about different things.  I'm talking about
> when planet.rb reads data from the database and puts it in the planet
> file.  This has nothing to do with writing changes into the database
> where (as you say) the database or API code should assign its own
> timestamp without trusting the client.
>
> The database itself doesn't require a timestamp "format" because dates
> aren't stored as strings, they're stored in a MySQL timestamp field.

If timestamps aren't stored as strings, why do you get different
formats depending on which client created the object?

-- 
-- 
Robert Hart




More information about the dev mailing list