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

From Durumdara
Subject PLPGSQL - extra column existence in trigger
Date
Msg-id CAEcMXhmO-FjavfjRwf6+sbR-FV_RPyG14gR7H5G+yM3u6J=udg@mail.gmail.com
Whole thread Raw
Responses Re: PLPGSQL - extra column existence in trigger
Re: PLPGSQL - extra column existence in trigger
List pgsql-general
Hello!

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:

select username, userid, usercompname 
   into uname, uid, ucomp from tmp_userauth limit 1;

or 

FOR rec IN 
  select * from tmp_userauth limit 1 ...  IF ColumnExists(rec, 'uid') THEN  --- ????     uid = rec.uid

So what is the best way to load the field values from the table?

Is there any way to know which field exists / avoid error or exception?

select username, getvaluewithouterror(userid, -1)...

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

Thank you!

Best regards,
   dd

pgsql-general by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: pg_dump: VACUUM and REINDEXING
Next
From: Hasan Marzooq
Date:
Subject: Re: pg_dump: VACUUM and REINDEXING