[please trim current@ from the CC list on reply]
> IMHO the SQL code you quote in the PR should fail with an ``invalid
> time'' error.
There's some truth to that... but Apr 7th 2am -8:00 isn't an invalid
datetime. It isn't correct, Apr 7th 3am -7:00 is the correct time,
but they're identical b
Hi,
I've cc'd -standards as I think this would be of interest there.
IMHO the SQL code you quote in the PR should fail with an ``invalid
time'' error.
Personally I like the fact that mktime() returns -1 - it allows
date's -v option to act sanely, although I must admit it was a PITA
to get ri
I haven't read POSIX yet, but mktime() fails on the boundary condition
blackholes when timezones change. I just filed a patch for the
PostgreSQL port so that it deals with this problem.
http://www.freebsd.org/cgi/query-pr.cgi?pr=36954
I believe that Linux and SunOS handle this automatically and
