Re: How to efficiently make an "history" ?

> >> Furthermore, when a user, from the front-end, updates a particular
> column [sic: field], we want to have a revision commentmand to keep
> all old data i.e. change 'name' from 'james' to 'bob' with revision
> comment 'he prefers shorter names...'. <<
>
> Don't do this -- use a log file if you need to follow the history and
> keep a separate text file with this useless commentary.

I think we can't judge which data is useless in Kesako's business. As Kesako is planning to register the commentary, he/she has already probably considered the information as worth saving.

This looks like a revision history issue. Have you been looking the existing version control software products (eg Merant PVCS, Microsoft VSS)? They may give you some ideas. If the columns in tables are fixed, you can store new revisions as new rows, identify them with InsertionDate, and have a column for the commentary.

Matti Received on Thu Aug 30 2001 - 09:44:21 CEST