Re: log database changes - a design problem? - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: log database changes - a design problem?
Date
Msg-id 20061123100213.GA1212@svana.org
Whole thread Raw
In response to log database changes - a design problem?  (Luca Ferrari <fluca1978@infinito.it>)
List pgsql-general
On Thu, Nov 23, 2006 at 08:53:28AM +0100, Luca Ferrari wrote:
> Hi all,
> I've got my database on which I'm building a Java application. Since I'd like
> to store information about who inserted and updated a specified record, I
> placed in my main tables a few additional fields to store such information:

<snip>

> Here comes my question: how can I catch user changes to each record in the
> database without be bored with user/date details? Anyone can suggest me  a
> smart solution and/or database design? Anyone has already found such kind of
> problem?

Sounds like something a trigger would be good for.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment

pgsql-general by date:

Previous
From: Arnaud Lesauvage
Date:
Subject: Re: MSSQL to PostgreSQL : Encoding problem
Next
From: Andreas Kretschmer
Date:
Subject: Re: log database changes - a design problem?