Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql General > Re: Is this pos...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 2 of 8 Topic 15474 of 16554
Post > Topic >>

Re: Is this possible in a trigger?

by kgore4@[EMAIL PROTECTED] (Klint Gore) May 7, 2008 at 10:10 AM

Fernando wrote:
> I want to keep a history of changes on a field in a table.  This will 
> be the case in multiple tables.
>
> Can I create a trigger that loops the OLD and NEW values and compares 
> the values and if they are different creates a change string as follows:
>
> e.g;
>
> FOR EACH field IN NEW
>     IF field.value <> OLD.field.name THEN
>        changes := changes
>             || field.name
>             || ' was: '
>             || OLD.field.value
>             || ' now is: '
>             || field.value
>             || '\n\r';
>     END IF
> END FOR;
>
> Your help is really appreciated.
You can't in plpgsql.  It doesn't have the equivalent of a walkable 
fields collection.  Its possible in some other procedure languages (I've 
seen it done in C).

Having said that, you might be able to create new and old temp tables 
and then use the system tables to walk the columns list executing sql to 
check for differences.

something like

   create temp table oldblah as select old.*;
   create temp table newblah as select new.*;
   for arecord in
        select columnname
        from pg_??columns??
        join pg_??tables?? on ??columns??.xxx = ??tables??.yyy
       where tablename = oldblah and pg_table_is_visible
   loop

        execute 'select old.' || arecord.columname || '::text , new. ' 
|| arecord.columname || '::text' ||
                    ' from oldblah old, newblah new ' ||
                    ' where oldblah.' || arecord.columnname || ' <> 
newblah.' ||arecord.columnname    into oldval,newval;

       changes := changes || arecord.columnname || ' was ' || oldval || 
' now ' || newval;
   end loop;
   execute 'drop table oldblah';
   execute 'drop table newblah';

performance could be awful though.

klint.

-- 
Klint Gore
Database Manager
Sheep CRC
A.G.B.U.
University of New England
Armidale NSW 2350

Ph: 02 6773 3789  
Fax: 02 6773 3266
EMail: kgore4@[EMAIL PROTECTED]
 
Sent via pgsql-general mailing list (pgsql-general@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
 




 8 Posts in Topic:
Is this possible in a trigger?
fernando@[EMAIL PROTECTED  2008-05-06 17:05:37 
Re: Is this possible in a trigger?
kgore4@[EMAIL PROTECTED]   2008-05-07 10:10:50 
Re: Is this possible in a trigger?
kreno@[EMAIL PROTECTED]   2008-05-06 19:13:29 
Re: Is this possible in a trigger?
xzilla@[EMAIL PROTECTED]   2008-05-07 01:12:25 
Re: Is this possible in a trigger?
fernando@[EMAIL PROTECTED  2008-05-07 09:37:21 
Re: Is this possible in a trigger?
kreno@[EMAIL PROTECTED]   2008-05-07 08:16:01 
Re: Is this possible in a trigger?
depesz@[EMAIL PROTECTED]   2008-05-07 13:01:35 
Re: Is this possible in a trigger?
valgog <valgog@[EMAIL   2008-05-07 04:04:21 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Sun Sep 7 1:33:22 CDT 2008.