MIME-Version: 1.0
References: <CAD=mzVU0rx4A0onfC4jHxZ7XreZrk9DNa9pFoGDOjPD1ZhfHgw@mail.gmail.com>
 <85cc2eb0ca709ab753e618584f46dbf8801e9658.camel@cybertec.at>
In-Reply-To: <85cc2eb0ca709ab753e618584f46dbf8801e9658.camel@cybertec.at>
From: sud <suds1434@gmail.com>
Date: Wed, 31 Jul 2024 00:16:01 +0530
Message-ID: <CAD=mzVVOC=H9zhYn5YF74XMV+7023f5hPvcroSaQu61m7q-yCg@mail.gmail.com>
Subject: Re: Trigger usecase
To: Laurenz Albe <laurenz.albe@cybertec.at>, 
	"David G. Johnston" <david.g.johnston@gmail.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000697635061e7b64a0"
Archived-At: <https://www.postgresql.org/message-id/CAD%3DmzVVOC%3DH9zhYn5YF74XMV%2B7023f5hPvcroSaQu61m7q-yCg%40mail.gmail.com>
Precedence: bulk

--000000000000697635061e7b64a0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 30, 2024 at 10:54=E2=80=AFPM Laurenz Albe <laurenz.albe@cyberte=
c.at>
wrote:

>
> It is largely a matter of taste.
>
> The advantage of a trigger is that it works even if somebody bypasses the
> application
> to insert data.
>
> I think that triggers are easy to debug, but again, that's a matter of
> taste.
>
>
> Thank you David and Laurenz.

Creating triggers to populates some audit table or say populating data in
audit columns (created_by, updated_by,created_date,updated_date) is fine i
believe, however this use case was to load/persist data in table with SCD-2
style, so is it good idea to use the trigger for such use case?

Not sure of the exact pros and cons, but we were following certain rules
like , if it's business logic which needs to be implemented in Database,
then it should not be done using triggers but rather should be done through
database procedure/functions. Hope this understanding correct.

Regards
Sud

--000000000000697635061e7b64a0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 30, 2024 at 10:54=E2=80=AFPM =
Laurenz Albe &lt;<a href=3D"mailto:laurenz.albe@cybertec.at">laurenz.albe@c=
ybertec.at</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><br>
It is largely a matter of taste.<br>
<br>
The advantage of a trigger is that it works even if somebody bypasses the a=
pplication<br>
to insert data.<br>
<br>
I think that triggers are easy to debug, but again, that&#39;s a matter of =
taste.<br>
<br><br></blockquote><div>Thank you David and Laurenz.</div><div><br></div>=
<div>Creating triggers to populates some audit table or say populating data=
 in audit columns (created_by, updated_by,created_date,updated_date) is fin=
e i believe, however=C2=A0this use case=C2=A0was to load/persist data in ta=
ble with SCD-2 style, so is it good idea to use the trigger for such use ca=
se?<br></div><div><br></div><div>Not sure of the exact pros and cons, but w=
e were following certain rules like , if it&#39;s business logic which need=
s to be implemented in Database, then it should not be done using triggers =
but rather should be done through database procedure/functions. Hope this u=
nderstanding=C2=A0correct.</div><div><br></div><div>Regards</div><div>Sud=
=C2=A0<br></div></div></div>

--000000000000697635061e7b64a0--