Message-ID: <85cc2eb0ca709ab753e618584f46dbf8801e9658.camel@cybertec.at>
Subject: Re: Trigger usecase
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: sud <suds1434@gmail.com>, pgsql-general
 <pgsql-general@lists.postgresql.org>
Date: Tue, 30 Jul 2024 19:24:06 +0200
In-Reply-To: <CAD=mzVU0rx4A0onfC4jHxZ7XreZrk9DNa9pFoGDOjPD1ZhfHgw@mail.gmail.com>
References: 
	<CAD=mzVU0rx4A0onfC4jHxZ7XreZrk9DNa9pFoGDOjPD1ZhfHgw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.52.3 (3.52.3-1.fc40) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/85cc2eb0ca709ab753e618584f46dbf8801e9658.camel%40cybertec.at>
Precedence: bulk

On Tue, 2024-07-30 at 20:46 +0530, sud wrote:
> Now while loading transactions data we also get some reference data infor=
mation from
> source (for example customer information) and for these , we dont want to=
 modify or
> override the existing customer data but want to keep the old data with a =
flag as
> inactive and the new record should get inserted with flag as active. So f=
or such
> use case , should we cater this inside the apache flink application code =
or should
> we handle this using trigger on the table level which will execute on eac=
h INSERT
> and execute this logic?=C2=A0
>=20
> I understand trigger is difficult to debug and monitor stuff. But here in=
 this case ,
> team mates is saying , we shouldn't put such code logic into a streaming =
application
> code so should rather handle through trigger.=C2=A0
>=20
> I understand, technically its possible bith the way, but want to understa=
nd experts
> opinion on this and pros ans cons?

It is largely a matter of taste.

The advantage of a trigger is that it works even if somebody bypasses the a=
pplication
to insert data.

I think that triggers are easy to debug, but again, that's a matter of tast=
e.

Yours,
Laurenz Albe