Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Exclude constraint on ranges : commutative containment : allow only complete containment
From: Michael Lewis <mlewis@xxxxxxxxxxx>
Date: Wed, 29 Jan 2020 11:43:29 -0700
Cc: Achilleas Mantzios <achill@xxxxxxxxxxxxxxxxxxxxx>, PostgreSQL General <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <a1596542-a70f-818e-7f65-280837da31f5@aklaver.com>
References: <3b555944-1563-6614-a5d5-e0cc001aecdb@matrix.gatewaynet.com> <a1596542-a70f-818e-7f65-280837da31f5@aklaver.com>

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?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Exclude constraint on ranges : commutative containment : allow only complete containment
  - From: Achilleas Mantzios

References:
- Exclude constraint on ranges : commutative containment : allow only complete containment
  - From: Achilleas Mantzios
- Re: Exclude constraint on ranges : commutative containment : allow only complete containment
  - From: Adrian Klaver

Prev by Date: Re: Exclude constraint on ranges : commutative containment : allow only complete containment
Next by Date: Re: Performance Issue after upgrade from 9 to 11
Previous by thread: Re: Exclude constraint on ranges : commutative containment : allow only complete containment
Next by thread: Re: Exclude constraint on ranges : commutative containment : allow only complete containment
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]