Search Postgresql Archives

Keeping historical record changes w/ triggers - best practices?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have a wide-ish table with 60 columns. I want to make a copy of data whenever a record is updated or deleted.

Right now I have a table that's almost identical but with a 'created' column (timestamp) and an 'action' column (which gets TG_OP for UPDATE or DELETE).

My idea would be to sort on the created column to see the historical record by comparing the columns. My other thought is to create two columns for each column in the master table (old_column, new_column, etc), storing the old values and the new values, and see what's changed that way.

The other idea, probably a terrible idea, was to use hstore to create a list of the old values and new values, and have this history table just be the timestamp, action, and two hstore columns.

Surely this has been done thousands of times. What are the thoughts regarding best practices in PG?

Thanks everyone.

--
Wells Oliver
wellsoliver@xxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux