Skip site navigation (1) Skip section navigation (2)

Re: Timestamp change - 8601 compliance

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Rod Taylor <rbt(at)barchord(dot)com>
Cc: Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Timestamp change - 8601 compliance
Date: 2001-06-06 20:55:42
Message-ID: 3B1E98CE.77156536@alumni.caltech.edu (view raw or flat)
Thread:
Lists: pgsql-hackers
> With XSDs right around the corner using ISO 8601 compliant dates, what
> are the chances Postgres could fully support them?

Good.

> 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.

The currently accepted date/time format *is* ISO-compliant. However,
there is the "machine interchange" (my quotes) version which has the
embedded "T" and "Z" fields.

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

Of course ;)

I have patches to support a "julian day" format (with a leading "J" or
"JD"), and istm that support for the "T" and "Z" fillers would be close
to trivial. I'll try some testing...

                         - Thomas

In response to

pgsql-hackers by date

Next:From: mlwDate: 2001-06-06 20:57:35
Subject: Re: REPLACE INTO table a la mySQL
Previous:From: Peter EisentrautDate: 2001-06-06 19:43:53
Subject: And what about that Debugfile?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group