Re: Top five challenges
От | silly sad |
---|---|
Тема | Re: Top five challenges |
Дата | |
Msg-id | 4D79C968.3080005@bestmx.ru обсуждение исходный текст |
Ответ на | Re: Top five challenges (Adrian Klaver <adrian.klaver@gmail.com>) |
Список | pgsql-advocacy |
On 03/10/11 20:52, Adrian Klaver wrote: > On 03/10/2011 09:57 AM, silly sad wrote: >> On 03/10/11 20:48, Adrian Klaver wrote: >>> On 03/10/2011 09:15 AM, silly sad wrote: >>>> On 03/10/11 20:07, Adrian Klaver wrote: >>>>> On 03/10/2011 08:53 AM, silly sad wrote: >>>>> >>>>> >>>>>>> >>>>>>> Well, 'epoch' clearly is a point in time with the hour being >>>>>>> midnight at >>>>>>> GMT, so I don't see a problem with epoch making such an adjustment: >>>>>> >>>>>> >>>>>> great! the flexible epoch! >>>>>> >>>>>> when do want to point an epoch to? >>>>>> just set timezone and enjoy. >>>>>> >>>>> >>>>> I am not sure what your point is. >>>> >>>> my point is: >>>> >>>> SELECT extract('epoch' from 'epoch'::timestamp); >>> >>> Simplest explanation is you are comparing a time zone aware datetime >>> 'epoch' to an unaware one 'epoch'::timezone. The second one, since it >>> is not anchored to a time zone is taken to be local time and the result >>> you get is the interval in seconds between the two. >> >> (1) do u really believe in this? >> (2) why didn't u try the select i wrote? > > Yes > I did. do u think the 'epoch' of 'epoch' should not be 0 ?
В списке pgsql-advocacy по дате отправления: