| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: log database changes - a design problem? |
| Date: | 2006-11-23 10:02:13 |
| Message-ID: | 20061123100213.GA1212@svana.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arnaud Lesauvage | 2006-11-23 10:04:46 | COPY FROM : out of memory |
| Previous Message | Arnaud Lesauvage | 2006-11-23 09:59:57 | Re: MSSQL to PostgreSQL : Encoding problem |