Re: Top five challenges
От | Adrian Klaver |
---|---|
Тема | Re: Top five challenges |
Дата | |
Msg-id | 4D79053D.1050309@gmail.com обсуждение исходный текст |
Ответ на | Re: Top five challenges (silly sad <sad@bestmx.ru>) |
Ответы |
Re: Top five challenges
|
Список | pgsql-advocacy |
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. The epoch being used is just one of many that could have been used, see link below. So by definition the term epoch is flexible. The Postgres project has chosen a particular value for 'epoch' as explained in the docs. This 'epoch' is a special datetime value pinned to a point in time(as Bruce mentioned). All adding a time zone does is translate the GMT point in time to the time zone point in time. They are the same time. http://en.wikipedia.org/wiki/Epoch_%28reference_date%29#Computing -- Adrian Klaver adrian.klaver@gmail.com
В списке pgsql-advocacy по дате отправления: