Search Postgresql Archives

Re: PLPGSQL - extra column existence in trigger

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: PLPGSQL - extra column existence in trigger
From: "David G. Johnston" <david.g.johnston@xxxxxxxxx>
Date: Sat, 7 May 2022 07:41:44 -0700
Cc: Postgres General <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <CAEcMXhmO-FjavfjRwf6+sbR-FV_RPyG14gR7H5G+yM3u6J=udg@mail.gmail.com>
References: <CAEcMXhmO-FjavfjRwf6+sbR-FV_RPyG14gR7H5G+yM3u6J=udg@mail.gmail.com>

On Saturday, May 7, 2022, Durumdara <durumdara@xxxxxxxxx> wrote:

So is there any syntax to not fall on missing columns?

No. I’d probably approach this by generically converting the NEW record to json and working with that. Non-existent object keys return null when accessed.

David J.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: PLPGSQL - extra column existence in trigger
  - From: hubert depesz lubaczewski
- Re: PLPGSQL - extra column existence in trigger
  - From: Durumdara

References:
- PLPGSQL - extra column existence in trigger
  - From: Durumdara

Prev by Date: Re: pg_dump: VACUUM and REINDEXING
Next by Date: Re: pg_dump: VACUUM and REINDEXING
Previous by thread: PLPGSQL - extra column existence in trigger
Next by thread: Re: PLPGSQL - extra column existence in trigger
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux