| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Stuart Campbell <stuart(dot)campbell(at)ridewithvia(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Capture a changelog for the current transaction |
| Date: | 2026-10-06 20:59:59 |
| Message-ID: | 25f24b18-0bc3-4a15-bb1c-fc3856f81fb6@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2026-10-06 21:38:00 | Re: AW: Why is materialized view creation a "security-restricted operation"? |
| Previous Message | Laurenz Albe | 2026-10-06 13:29:47 | Re: Capture a changelog for the current transaction |