Re: Capture a changelog for the current transaction - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Capture a changelog for the current transaction
Date
Msg-id 25f24b18-0bc3-4a15-bb1c-fc3856f81fb6@aklaver.com
Whole thread
In response to Capture a changelog for the current transaction  (Stuart Campbell <stuart.campbell@ridewithvia.com>)
Responses Re: Capture a changelog for the current transaction
List pgsql-general

On 10/6/26 3:38 AM, Stuart Campbell wrote:
> Hello,
> 
> Our data model has some constraints that are not enforceable at the 
> database level. So, we resort to running some checks in application code 
> at the end of each transaction.

Does this mean the information needed to do the checks is not in the 
database, but in another data store?


> Any guidance is appreciated.
> 
> Thanks,
> Stuart
> 
> This communication and any attachments may contain confidential 
> information and are intended to be viewed only by the intended 
> recipients. If you have received this message in error, please notify 
> the sender immediately by replying to the original message and then 
> delete all copies of the email from your systems.
> 
> 




pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Capture a changelog for the current transaction
Next
From: Adrian Klaver
Date:
Subject: Re: AW: Why is materialized view creation a "security-restricted operation"?