Re: BUG #4115: PostgreSQL ISO format is not really ISO
| От | Jaime Casanova |
|---|---|
| Тема | Re: BUG #4115: PostgreSQL ISO format is not really ISO |
| Дата | |
| Msg-id | c2d9e70e0804191010j78161731sbd24690522fbe509@mail.gmail.com обсуждение исходный текст |
| Ответ на | BUG #4115: PostgreSQL ISO format is not really ISO ("Daniel Ruoso" <daniel@ruoso.com>) |
| Ответы |
Re: BUG #4115: PostgreSQL ISO format is not really ISO
|
| Список | pgsql-bugs |
On Sat, Apr 19, 2008 at 6:38 AM, Daniel Ruoso <daniel@ruoso.com> wrote: > > The following bug has been logged online: > > Bug reference: 4115 > Logged by: Daniel Ruoso > Email address: daniel@ruoso.com > PostgreSQL version: 8.3.1 > Operating system: Debian GNU/Linux lenny > Description: PostgreSQL ISO format is not really ISO > Details: > > ISO8601[1] defines Date/Time ouput, and is, today, quite accepted, being = the > standard used by XML Schema definitions. Which means that they have to be= in > that format to be accepted by a XML validator. > > The basic difference between PostgreSQL format and the ISO format is the > absence of a "T" between the date and the time. > > [1] http://en.wikipedia.org/wiki/ISO_8601 > This says that a space between date and time is acceptable, although not considered a single field. http://en.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_representations """ Unlike the previous examples, "2007-04-05 14:30" is considered two separate, but acceptable, representations=97one for date and the other for time. It is then left to the reader to interpret the two separate representations as meaning a single time point based on the context. """ --=20 regards, Jaime Casanova Soporte de PostgreSQL Guayaquil - Ecuador Cel. 087171157
В списке pgsql-bugs по дате отправления: