Timestamp change - 8601 compliance

Поиск
Список
Период
Сортировка
От Rod Taylor
Тема Timestamp change - 8601 compliance
Дата
Msg-id 017801c0eea3$be5475a0$1600a8c0@jester
обсуждение исходный текст
Список pgsql-hackers
With XSDs right around the corner using ISO 8601 compliant dates, what
are the chances Postgres could fully support them?

The primary difference between that and what it does now is a T for
the date / time seperator rather than a space and the potential for a
Z for the timezone seperator.

I'm convinced this was done to piss me off and enforce conversion
routines for databases to actually accept the information passed.

Info:

1999-05-31T13:20:00.000-05:00

May 31st 1999 at 1.20pm Eastern Standard Time which is 5 hours behind
Co-Ordinated Universal Time

http://www.cs.utsa.edu/~wagner/date/8601.pdf
http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#dateTime
--
Rod Taylor

Your eyes are weary from staring at the CRT. You feel sleepy. Notice
how restful it is to watch the cursor blink. Close your eyes. The
opinions stated above are yours. You cannot imagine why you ever felt
otherwise.


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "rai lalit"
Дата:
Сообщение: Delete oid causing problems
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Can the backend return more than one error message per PQexec?