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

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Exclude constraint on ranges : commutative containment : allow only complete containment
Date: 2020-01-30 22:16:51
Message-ID: 6a61a14d-21ba-4804-9ab4-329c9740af7c@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2020-01-30 22:23:15 How to restore to empty database
Previous Message Adrian Klaver 2020-01-30 22:11:48 Re: Options for Postgres FDW