Re: Bug #679: Time input format is no longer ISO 8601 compliant

Malcolm Tredinnick (malcolm(at)commsecure(dot)com(dot)au) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
Time input format is no longer ISO 8601 compliant

Long Description
Using PostgreSQL 7.2 on a Red Hat 7.3 system (also fails with PostgreSQL 7.2 on a Red Hat 7.2 system)...

According to the PostgreSQL manual (the section on Date/Time input), it should be possible to enter 'time' fields as "100000" for 10:00:00.

This was certainly possible in 7.1, but it now raises a "Bad time external representation '100000'" error with 7.2. This format is certainly permitted by ISO 8601, so I am suspecting a coding error, rather than some adjustments for standards compliance (if it is the latter, then the documentation needs to be updated).

Sample Code
create table foo (
mydate time
);

insert into foo (mydate) values ('100000'); -- fails in PostgreSQL 7.2
insert into foo (mydate) values ('10:00:00'); -- still works in 7.2

No file was uploaded with this report

> ... it should be possible to enter 'time' fields as "100000" for 10:00:00.

Try prepending a "T" to the front of the string (also allowed per
ISO-8601). Will be fixed in the next release to allow the number-only
form.

- Thomas