On Jun 4, 2011, at 3:56 AM, Greg Stark wrote: > On Thu, Jun 2, 2011 at 8:58 PM, Jim Nasby <j...@nasby.net> wrote: >> >> I'm torn between whether the type should store the original time or the >> original time converted to GMT. > > This is the wrong way to think about it. We *never* store time > "converted to GMT". When we want to represent a point in time we > represent it as seconds since the epoch. Right. Sorry, my bad.
> The question here is how to represent more complex concepts than > simply points in time. I think the two concepts under discussion are > a) a composite type representing a point in time and a timezone it > should be interpreted in for operations and display and b) the > original input provided which is a text string with the constraint > that it's a valid input which can be interpreted as a point in time. My fear with A is that something could change that would make it impossible to actually get back to the time that was originally entered. For example, a new version of the timezone database could change something. Though, that problem also exists for timestamptz today, so presumably if it was much of an issue we'd have gotten complaints by now. -- Jim C. Nasby, Database Architect j...@nasby.net 512.569.9461 (cell) http://jim.nasby.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
