| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Comparing dates in DDL |
| Date: | 2019-01-04 23:59:07 |
| Message-ID: | alpine.LNX.2.20.1901041557080.29312@salmo.appl-ecosys.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 4 Jan 2019, Jeremy Finzel wrote:
> Another suggestion which hasn’t been mentioned is using ‘infinity’ as the
> end date. I like this because it IMO indicates that the record is clearly
> the current valid record more than null.
Jeremy,
I believe that infinity was mentioned in this thread.
> But I’m not sure exactly what you are trying to do either. If you are
> creating a new record with changes and closing (ending) the range of the
> original record, then a GIST exclusion index would ensure you have no
> overlapping date ranges for all historical records put together.
Having overlapping date ranges in a projects table is a Good Thing(TM)
because it means I have multiple, concurrent revenue streams. :-)
Carpe weekend,
Rich
--
I dream of an America where a chicken can cross the road without having its
motives questioned.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Allison Kaptur | 2019-01-05 00:28:51 | ALTER TABLE with multiple SET NOT NULL |
| Previous Message | Jeremy Finzel | 2019-01-04 23:49:17 | Re: Comparing dates in DDL |