Feedback-ID: i76984098:Fastmail
Message-ID: <55d5e0db-f80a-4253-8c21-9b7b6c6a2f4d@aklaver.com>
Date: Sun, 25 Aug 2024 08:33:41 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: On exclusion constraints and validity dates
To: Justin Giacobbi <jgiacobbi@optionmetrics.com>,
 "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: <BYAPR01MB4374D78F63C66F0ED4178696A18F2@BYAPR01MB4374.prod.exchangelabs.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <BYAPR01MB4374D78F63C66F0ED4178696A18F2@BYAPR01MB4374.prod.exchangelabs.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/55d5e0db-f80a-4253-8c21-9b7b6c6a2f4d%40aklaver.com>
Precedence: bulk

On 8/22/24 11:13, Justin Giacobbi wrote:
> Hello,
> 

> Currently I’m looking at working around this in the application or in a 
> stored procedure/insert trigger that is essentially the same logic. 
> Whichever seems easier to maintain.
> 
> Advice on how to submit a feature request, or maybe a better workaround 
> that I haven’t discovered would be most welcome. What would be even more 
> welcome is someone with insight into these pieces of the program that 
> can tell me if I’d be biting off more than I can chew (or violating a 
> principle) trying to submit one of the three options above as a feature.

Merge?:

https://www.postgresql.org/docs/current/sql-merge.html

> 
> Thank you
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com