From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Jim Nasby <jim(at)nasby(dot)net>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch: make_timestamp function |
Date: | 2013-12-17 16:56:22 |
Message-ID: | CAFj8pRB9nnWFWCPh+URK98wxvJrKChjU7i8wZz464=OjNdm0Hw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2013/12/17 Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
> Pavel Stehule escribió:
>
> > but AT TIME ZONE allows double (but decimal parts is ignored quietly)
> >
> > postgres=# select make_time(10,20,30) at time zone '+10.2';
> > timezone
> > -------------
> > 23:20:30-10
> >
> > so I propose (and I implemented) a variant with int as time zone
> >
> > and we can (if we would) implement next one with text as time zone
>
> Yeah, I think a constructor should allow a text timezone.
>
is there some simple way, how to parse text time zone?
Regards
Pavel
>
> --
> Álvaro Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-12-17 17:03:27 | Re: row security roadmap proposal |
Previous Message | Heikki Linnakangas | 2013-12-17 16:54:43 | Re: ANALYZE sampling is too good |