Re: PLPGSQL - extra column existence in trigger - Mailing list pgsql-general

From Peter J. Holzer
Subject Re: PLPGSQL - extra column existence in trigger
Date
Msg-id 20220510224354.r3lxpih7nhy5oi4w@hjp.at
Whole thread Raw
In response to PLPGSQL - extra column existence in trigger  (Durumdara <durumdara@gmail.com>)
Responses Re: PLPGSQL - extra column existence in trigger
List pgsql-general
On 2022-05-07 15:02:09 +0200, Durumdara wrote:
> We stored the username in a temporary table which was created by the client
> app.
> With this technique we can log these names in triggers too.
>
> Now we extend it with user id and later the comp name.
>
> Because we can update the client applications slowly, some client's tables have
> these one or two extra fields, some not.
>
> 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?

        hp

--
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"

Attachment

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Fedora 36
Next
From: Bryn Llewellyn
Date:
Subject: Deferred constraint trigger semantics