From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Justin Giacobbi <jgiacobbi(at)optionmetrics(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: On exclusion constraints and validity dates |
Date: | 2024-08-25 15:33:41 |
Message-ID: | 55d5e0db-f80a-4253-8c21-9b7b6c6a2f4d@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Marcelo Zabani | 2024-08-25 15:36:18 | Re: ERROR: could not open relation with OID XXXX |
Previous Message | Tomas Vondra | 2024-08-25 15:06:46 | Re: ERROR: could not open relation with OID XXXX |