We have a TODO also:
o Allow TIMESTAMP WITH TIME ZONE to store the original timezone
information, either zone name or offset from UTC [timezone]
If the TIMESTAMP value is stored with a time zone name, interval
computations should adjust based on the time zon
On Fri, Dec 16, 2005 at 11:25:22PM +0100, Martijn van Oosterhout wrote:
> On Fri, Dec 16, 2005 at 03:18:04PM -0600, Jim C. Nasby wrote:
> > BTW, if you wanted a more integrated solution, you could build a custom
> > type that would store the timestamp info. There's a good chance such
> > code would
On Fri, Dec 16, 2005 at 03:18:04PM -0600, Jim C. Nasby wrote:
> BTW, if you wanted a more integrated solution, you could build a custom
> type that would store the timestamp info. There's a good chance such
> code would end up being what's used in the server as the official type,
> too.
Well, I wr
BTW, if you wanted a more integrated solution, you could build a custom
type that would store the timestamp info. There's a good chance such
code would end up being what's used in the server as the official type,
too.
On Fri, Dec 16, 2005 at 08:57:04AM -0800, Andrew B. Young wrote:
> I just realiz
I just realized that the type "timestamp with time zone" does NOT store
the time zone!
(And I just found this support list to look for help.)
I am developing an application that stores power (watts) readings from
meters
located around the world (abridged)--
power_meter_id integer NOT NULL,
