From: | tgl(at)postgresql(dot)org |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/src/backend/utils/adt (timestamp.c date.c) |
Date: | 2000-12-07 18:38:59 |
Message-ID: | 200012071838.eB7IcxU92517@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Date: Thursday, December 7, 2000 @ 13:38:59
Author: tgl
Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/utils/adt
from hub.org:/home/projects/pgsql/tmp/cvs-serv92502/backend/utils/adt
Modified Files:
timestamp.c date.c
----------------------------- Log Message -----------------------------
Make OVERLAPS operators conform to SQL92 spec regarding NULL handling.
As I read it, the spec requires a non-null result in some cases where
one of the inputs is NULL: specifically, if the other endpoint of that
interval is between the endpoints of the other interval, then the result
is known TRUE despite the missing endpoint. The spec could've been a
lot simpler if they did not intend this behavior.
I did not force an initdb for this change, but if you don't do one you'll
still see the old strict-function behavior.
From | Date | Subject | |
---|---|---|---|
Next Message | tgl | 2000-12-07 19:40:56 | pgsql/src/backend/catalog (pg_proc.c) |
Previous Message | Vince Vielhaber | 2000-12-07 10:30:12 | [WEBMASTER] 'www/html mirrors.html' |