| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Alex Page <alex(dot)page(at)cancer(dot)org(dot)uk> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Versioning control in PostgreSQL? |
| Date: | 2003-10-28 16:40:37 |
| Message-ID: | Pine.LNX.4.33.0310280940070.19359-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 28 Oct 2003, Alex Page wrote:
> I haven't used PostgreSQL for nearly a year now, and when I was last
> using it there was some discussion on versioning control being
> introduced as a feature. Basically, for some data, I'd like to keep
> track of who changed it, when, and to what. I know I could include
> multiple values in the schema, and have a view to pull out the most
> recent, but I was wondering if there was something more automatic that
> is a feature of PostgreSQL itself. I've looked around the documentation
> with no success. Does anybody know if this is possible?
There's a nice example code in contrib/spi that might help here.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Chapman | 2003-10-28 16:51:04 | Re: [OT] Choosing a scripting language. |
| Previous Message | Tom Lane | 2003-10-28 15:59:39 | Re: SELECT with row>32k hangs over SSL-Connection |