Timestamp change - 8601 compliance 
Author Message
 Timestamp change - 8601 compliance

This is a multi-part message in MIME format.

------=_NextPart_000_0173_01C0EE82.335547C0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

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{*filter*}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.***.com/ ~wagner/date/8601.pdf
http://www.***.com/ #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.

------=_NextPart_000_0173_01C0EE82.335547C0
Content-Type: text/x-vcard; name="Taylor, Rod B.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="Taylor, Rod B.vcf"

BEGIN:VCARD
VERSION:2.1
N:Taylor;Rod;B
FN:Taylor, Rod B
ORG:BarChord Entertainment Inc.;System Operation and Development
TITLE:Chief Technical Officer
ADR;WORK:;;;Toronto;Ontario;;Canada
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Toronto, Ontario=0D=0ACanada
X-WAB-GENDER:2
URL;WORK: http://www.***.com/
BDAY:19790401



REV:20010606T161413Z
END:VCARD

------=_NextPart_000_0173_01C0EE82.335547C0
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
MIME-Version: 1.0

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command

------=_NextPart_000_0173_01C0EE82.335547C0--



Mon, 24 Nov 2003 00:51:23 GMT
 Timestamp change - 8601 compliance

Quote:
> With XSDs right around the corner using ISO 8601 compliant dates, what
> are the chances Postgres could fully support them?

Good.

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

Quote:
> I'm convinced this was done to{*filter*}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

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster



Mon, 24 Nov 2003 04:58:35 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. error 8601

2. Getting 2002-12-18T17:32:40-05:00 (ISO 8601) from to_date()

3. ISO 8601 Week Number Stored Procedures

4. Getting 2002-12-18T17:32:40-05:00 (ISO 8601) from to_date()

5. Calculating week and year according to ISO 8601 - week.txt (0/1)

6. Getting 2002-12-18T17:32:40-05:00 (ISO 8601) from

7. Bulk Loading ISO 8601 Date fields

8. Sybase Changes Postion on SQL Server Y2K Compliance?

9. Timestamp nanoseconds change when retrieved

10. Change from Summer to Wintertime / Timestamps

11. Timestamp never change

12. timestamp changed on 7.1.1 ?


 
Powered by phpBB® Forum Software