| From: | DAVID ROTH <adaptron(at)comcast(dot)net> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Trigger Function question |
| Date: | 2023-07-10 18:46:01 |
| Message-ID: | 108381110.172129.1689014761308@connect.xfinity.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I saw your message about a "few" columns and missed the new.* notation.
Is there a way to get new.* into a jsonb column?
> On 07/10/2023 2:38 PM EDT Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
> > On Jul 10, 2023, at 11:37, DAVID ROTH <adaptron(at)comcast(dot)net> wrote:
> >
> > Thanks for the example. I have a test trigger now that does that but my application needs all of the columns.
>
> I'm not quite sure I understanding. Logging NEW.* and OLD.* *does* get all the columns, without having to specific query to find out which columns the table that cause the trigger to fire has.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcos Pegoraro | 2023-07-10 18:51:14 | Re: Trigger Function question |
| Previous Message | DAVID ROTH | 2023-07-10 18:42:00 | Re: Trigger Function question |