Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon3.gif   Feature request, posted by Nick on Tue Feb 11 11:26:03 2003 
    icon3.gif   Re: Feature request, posted by Stefan Ritt on Tue Feb 11 11:45:22 2003 
       icon2.gif   Re: Feature request, posted by Nick on Wed Feb 12 01:11:08 2003 
          icon2.gif   Re: Feature request, posted by Stefan Ritt on Wed Feb 12 08:54:05 2003 
Message ID: 219     Entry time: Wed Feb 12 08:54:05 2003     In reply to: 218
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Info  OS:   ELOG Version:  
Subject: Re: Feature request 
> > > Can you consider implementing the following additions to the 
functionality
> > > 
> > > 1) Subt on edit <attribute> = xyz 
> > > 
> > > This would be fantastic for implementing version control so you can see 
> > who 
> > > has edited a posted or a db entry.
> > 
> > Can you give me an example of how you would use that?
> 
> -----
> 
> Lets say you are storing configuration information relating to a customers 
> solution, you need the ability to track who has made what changes to the 
> config information stored in the log book so you can backtrack who changed 
> what and when, for example
> 
> If you have a field name called Last Edited by this field is locked and not 
> editable using the Lock attributes flag, but if you had Subt on edit 
> everytime that entry is updated it places your login name into this field 
and 
> therefore stamps it to say you have edited it, as the field isnt free txt 
it 
> cant be spoofed as the $long_name comes from your login details.

Ok, I implemented "Subst on edit", it will be contained in Version 2.3.1 
which is supposed to come out next week.

- Stefan
ELOG V3.1.5-fe60aaf