diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2000-12-07 18:38:59 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2000-12-07 18:38:59 +0000 |
| commit | 821f4673ffa53ddfb792cbf646783037dd6796ca (patch) | |
| tree | b7c090084a6fe4ed59f779878c90e9b84d26c97b /src/backend/commands/dbcommands.c | |
| parent | 8bb4dab94d26e330cc1f0327b99753d89f5c90ee (diff) | |
| download | postgresql-821f4673ffa53ddfb792cbf646783037dd6796ca.tar.gz postgresql-821f4673ffa53ddfb792cbf646783037dd6796ca.zip | |
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.
Diffstat (limited to 'src/backend/commands/dbcommands.c')
0 files changed, 0 insertions, 0 deletions