MIME-Version: 1.0
References: <CAB+=1TWT1_kKdBtuWvLBKJ1hkjxsaRZfMQADQU7bsVtat9q-LA@mail.gmail.com>
 <Zmg2GIso2Lb4r_2m@depesz.com> <CAB+=1TUWFJ_9BsqVZkj+3V18WxpAZojzhbOLN1kGzUYqx=TLfQ@mail.gmail.com>
 <CANzqJaDrByG6Pbi70tK2j_8KP1P6TvF5XoAhSLDVMpCwNhFn4A@mail.gmail.com>
In-Reply-To: <CANzqJaDrByG6Pbi70tK2j_8KP1P6TvF5XoAhSLDVMpCwNhFn4A@mail.gmail.com>
From: Isaac Morland <isaac.morland@gmail.com>
Date: Wed, 12 Jun 2024 12:40:03 -0400
Message-ID: <CAMsGm5dqHQ_Sg5wgYg3mXJfOXPrGTK1s2cmNzEriNuAeQt=6NQ@mail.gmail.com>
Subject: Re: Does trigger only accept functions?
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000a2e093061ab409c0"
Archived-At: <https://www.postgresql.org/message-id/CAMsGm5dqHQ_Sg5wgYg3mXJfOXPrGTK1s2cmNzEriNuAeQt%3D6NQ%40mail.gmail.com>
Precedence: bulk

--000000000000a2e093061ab409c0
Content-Type: text/plain; charset="UTF-8"

On Tue, 11 Jun 2024 at 18:25, Ron Johnson <ronljohnsonjr@gmail.com> wrote:

Since all the functions are going to be similar, I'd write a shell script
> to generate all the triggers, one per relevant.  If you're going to record
> every field, then save effort, and don't bother enumerating them.  You'll
> need to dig into the PG catalog's guts to list columns in the correct
> order, but Google and Stack Exchange makes that easy enough.
>

I'd use a DO block and write a loop in PL/PGSQL. Then everything stays in
Postgres and you have all the support of Postgres when writing your
SQL-writing code (quote_ident, the reg* types, etc.).

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

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, 11 Jun 2024 at 18:25, Ron Johnson=
 &lt;<a href=3D"mailto:ronljohnsonjr@gmail.com">ronljohnsonjr@gmail.com</a>=
&gt; wrote:<br></div><div class=3D"gmail_quote"><div><br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div></div><div>Since all =
the functions are going to be similar, I&#39;d write a shell script to gene=
rate all the triggers,=C2=A0one per relevant.=C2=A0 If you&#39;re going to =
record every field, then save effort, and don&#39;t bother enumerating them=
.=C2=A0 You&#39;ll need to dig into the PG catalog&#39;s guts to list colum=
ns in the correct order, but Google and Stack Exchange makes that easy enou=
gh.</div></div></div></blockquote><div><br></div><div>I&#39;d use a DO bloc=
k and write a loop in PL/PGSQL. Then everything stays in Postgres and you h=
ave all the support of Postgres when writing your SQL-writing code (quote_i=
dent, the reg* types, etc.).</div></div></div>

--000000000000a2e093061ab409c0--