| From: | Stuart Campbell <stuart(dot)campbell(at)ridewithvia(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Capture a changelog for the current transaction |
| Date: | 2026-10-06 23:56:06 |
| Message-ID: | CAAZ6Sny7Sif-TOfFZryFx1BWjNC=avZ8zsA9sXeQtTnSdYwC7g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Oct 7, 2026 at 8:00 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> 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?
Not exactly. Some of our tables hold binary data that can't be inspected
from within the databse. Our app has to deserialize the binary data and run
checks against it.
--
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 | Stuart Campbell | 2026-10-07 00:02:49 | Re: Capture a changelog for the current transaction |
| Previous Message | Adrian Klaver | 2026-10-06 21:50:03 | Re: Why is materialized view creation a "security-restricted operation"? |