From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | hernan gonzalez <hgonzalez(at)gmail(dot)com> |
Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Timezones (in 8.5?) |
Date: | 2009-11-29 01:40:43 |
Message-ID: | 200911290140.nAT1ehK07981@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
hernan gonzalez wrote:
> > hernan> The support of timezones is really crippled
> > ?hernan> now.
> >
> > Crippled how?
>
> Well, among other things, no builtin date-timetype allows me to save
> the timezone (or even the offset).
> No type allows to treat this three datetimes as different values.
> '2010-07-27 10:30 GMT+4' '2010-07-27 09:30 GMT+5' '2010-07-27 10:30 GMT+0'
> The ANSI spec at least permits that.
I think there is general agreement that we should have a timezone data
type which validates against pg_timezone_names().name. It might be
enough to just document how users can create such a domain data type,
but I don't know of a way to do that. Is this a TODO?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-11-29 02:19:42 | Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a |
Previous Message | Philip Warner | 2009-11-29 01:38:06 | Re: 8.5 TODO: Add comments to output indicating version of pg_dump and of the database server |