Re: Exclude constraint on ranges : commutative containment : allowonly complete containment - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Exclude constraint on ranges : commutative containment : allowonly complete containment
Date
Msg-id 6a61a14d-21ba-4804-9ab4-329c9740af7c@aklaver.com
Whole thread Raw
In response to Re: Exclude constraint on ranges : commutative containment : allowonly complete containment  (Achilleas Mantzios <achill@matrix.gatewaynet.com>)
List pgsql-general
On 1/30/20 9:03 AM, Achilleas Mantzios wrote:

>>
>> Um, that makes my head hurt:) Questions:
>>
>> 1) Are the basic complete budgets and the sub-budgets and super 
>> budgets existing in the same table?
>>
>> 2) Depending on answer to 1, to prevent overlap could you not use a 
>> form of the example here?:
>>
>> https://www.postgresql.org/docs/12/rangetypes.html#RANGETYPES-CONSTRAINT
>>
>> CREATE TABLE reservation (
>>     during tsrange,
>>     EXCLUDE USING GIST (during WITH &&)
>> );
>>
> same table.
> overlap is allowed but only when it is complete containment, which is 
> the whole point of this thread.
> 

I finally got it. Unfortunately that does not mean I have solution.


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Options for Postgres FDW
Next
From: "Andrus"
Date:
Subject: How to restore to empty database