Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Rob Sargent <robjsargent@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Manual query vs trigger during data load
Date: Fri, 13 Sep 2024 13:22:53 -0400
Message-Id: <BD545781-5E87-4CCB-A378-64B4C9F9AD2F@gmail.com>
References: <67f2a664-b480-40ea-892d-2ab2147ad390@aklaver.com>
Cc: Juan Rodrigo Alejandro Burgos Mella <rodrigoburgosmella@gmail.com>,
 yudhi s <learnerdatabase99@gmail.com>,
 pgsql-general <pgsql-general@lists.postgresql.org>
In-Reply-To: <67f2a664-b480-40ea-892d-2ab2147ad390@aklaver.com>
To: Adrian Klaver <adrian.klaver@aklaver.com>
Archived-At: <https://www.postgresql.org/message-id/BD545781-5E87-4CCB-A378-64B4C9F9AD2F%40gmail.com>
Precedence: bulk


> On Sep 13, 2024, at 10:57=E2=80=AFAM, Adrian Klaver <adrian.klaver@aklaver=
.com> wrote:
>=20
> =EF=BB=BFOn 9/13/24 07:50, Adrian Klaver wrote:
>>> On 9/13/24 02:58, Juan Rodrigo Alejandro Burgos Mella wrote:
>>> Hello, I find it unlikely that the trigger will work properly, since the=
 reserved fields of the OLD subset have no value in an INSERT
>> I'm not seeing that the OP is asking for OLD.* values, they are just look=
ing to include the result of a lookup on another table in the INSERT.
>=20
> My mistake I see the OLD reference now.
>=20
>>>=20
Personally I would cache the lookup on the java side a send the correct valu=
e to a simple insert statement

>=20
>=20
>=20