Re: Exclude constraint on ranges : commutative containment : allow only complete containment

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Exclude constraint on ranges : commutative containment : allow only complete containment
Date: 2020-01-29 18:43:29
Message-ID: CAHOFxGrXzOqCvsCc06=BMTNpAE+n+75ewtYJkDuLZ15o8c7mVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

If the new value does not overlap with any existing, allow. If it does
overlap, then it must be fully contained by the existing element, or the
existing element must be fully contained by it. Else, reject. Is that right?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Perumal Raj 2020-01-29 21:58:47 Re: Performance Issue after upgrade from 9 to 11
Previous Message Adrian Klaver 2020-01-29 18:32:09 Re: Exclude constraint on ranges : commutative containment : allow only complete containment