Audit trail

[jkkenzie]

I would like to keep an audit trail of changes made on a mysql database. The users use forms on pages to manipulate the records, i assume the audit trails happens on the form.

 

Any idea?

 

Joseph

[JonnoTheDev]

Store the users details and date modified in another database table.

I assume all users have a login and a unique ID.

For example you may have a table called stockInfo that contains records that users can update via forms to change the level of stock in a shop. To track updates on records you could have a stockUserAudit table containing the stockId as a foreign key from the stockInfo table, a userId for which user updated the stock record and a datetime field to capture the date of modification. You could easily create reports from this structure.

[jkkenzie]

That is how it normally is but what does the following mean?

 

action="/cgi-bin/write.plc"  on a form?

 

writing audit on a notepad or something like that is what i would like to try,

 

But what is the best practice?

 

Regards,

Jose

[JonnoTheDev]

eh? Are you a PHP developer?

 

This simply means that the form data will be sent to /cgi-bin/write.plc when posted.

write.plc must process the input

[jkkenzie]

Am still an infant in php programming.

 

Ill find out about .plc files. Thanks.

 

Am used to VBA where i write an audit of processes (that the user performed) to a text file. That is what am trying to try in php.

 

Does an audit trial involve DOUBLE DATA entry? i.e e.g saving a record on one table and saving audit trail of that record on another table WHEN the user saves a record?

 

Does this mean when am saving a record , i should have the logged in user details, with the process name ready to be saved on another table?

 

Thanks