> 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
