Re: Triggers should work in isolation, with a final conflict detection step

On Sunday, July 31, 2022, Gianluca Calcagni <gclazio(at)hotmail(dot)com> wrote:

>
> The real drawback is that such approach is forgoing the natural principle
> of *"separation of concerns"*! I have been looking into using trigger
> frameworks to solve this problem, but there is no trigger framework that is
> able to meet my main expectations: in short, *isolation* and *conflict
> detection*.
>
> You may notice that I took inspiration from GIT for most of the concepts
> above (e.g. "isolation" actually means "forking").
>
> I realize that this is a huge request,
>

So install a single c-language trigger function that does all of that and
provide some functions to manage adding delegation commands in user-space.
Make it all work with create extension. Users will have to adhere to the
guidelines suggested.

I am against having core incorporate such code into the main project. The
benefits/cost_complexity ratio is too small.

IOW, I suspect the only realistic way this gets into core is if you, its
champion, pay to have it developed, but even then I don’t think we should
accept such a feature even if it was well written. So if you go that route
it should leverage extension mechanisms. We may add some code hooks though
if those are requested and substantiated.

David J.