Re: Keeping information changes history - Mailing list pgsql-sql

From Tom Lane
Subject Re: Keeping information changes history
Date
Msg-id 16617.1011898802@sss.pgh.pa.us
Whole thread Raw
In response to Keeping information changes history  (Marius Andreiana <marius@wdg.ro>)
List pgsql-sql
Marius Andreiana <marius@wdg.ro> writes:
> I need to keep information changes history for people in our
> application.
> e.g. when their address was changed I need to remember who changed it
> (staff or member), when and to what was changed.

> I don't know what's the standard approach to this problem. I thought
> of having another address table, say addresses_history, same structure
> as usual table, but with some extra fields: type of user and user id who
> made the change, and time stamp.

> Every time a change is made to addresses table also insert the proper
> record in addresses_history with a trigger. But I need to know
> information about the user who changed it in database, not only the
> application, so where to keep it?
> So I should add other columns to addresses table for this (user id and
> type of user)

Yup, that's the standard approach, and using triggers to add entries to
the history table is exactly how it's done.
        regards, tom lane


pgsql-sql by date:

Previous
From: "Andrew G. Hammond"
Date:
Subject: Re: auto group by
Next
From: Oleg Lebedev
Date:
Subject: linking from SQL Server