| From: | Durumdara <durumdara(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PLPGSQL - extra column existence in trigger |
| Date: | 2022-05-23 17:14:25 |
| Message-ID: | CAEcMXhkwVw46F=nmQ8fD7n32DtPowZAnZAFqzWZFqwq+F6R=6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello!
Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> ezt írta (időpont: 2022. máj. 11., Sze,
0:44):
> On 2022-05-07 15:02:09 +0200, Durumdara wrote:
>
> > So in the new trigger we can't load them all with:
>
> How do you get a new trigger on one table but not the new columns on the
> other table? Wouldn't you update both at the same time?
>
The needed columns are in a temporary table. Each Win32 application creates
his own temp table with User Informations, like ID, Name, Computer Info.
These are for logging purposes.
The trigger is in another table, and I want to log the actual user
information with the row changing to see who caused it.
Best regards,
dd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2022-05-23 17:19:21 | Re: list tablespaces named in custom format dump |
| Previous Message | Adrian Klaver | 2022-05-23 17:07:04 | Re: list tablespaces named in custom format dump |