Hi,
On 8/12/2016 18:39, mach...@seworx.co.za wrote:
...
So to recap what has been done for now :
- Triggers to insert a record in audit table to show
the table, type of query(insert/update) and who made the relevant change.
- Trigger to prevent
<h...@tbbs.net>
To: "MySql" <mysql@lists.mysql.com>
Sent: Wednesday, 7 December, 2016 14:56:55
Subject: Re: audit trails
2016/12/07 01:26 ... mach...@seworx.co.za:
well in essence the following is required.
we need to know who made what changes to tables.
There is
sz" <h...@tbbs.net>
> To: "MySql" <mysql@lists.mysql.com>
> Sent: Wednesday, 7 December, 2016 14:56:55
> Subject: Re: audit trails
> 2016/12/07 01:26 ... mach...@seworx.co.za:
>> well in essence the following is required.
>>
>> we need to know wh
2016/12/07 01:26 ... mach...@seworx.co.za:
well in essence the following is required.
we need to know who made what changes to tables.
There is a machination that you can try in every trigger that will add
the user-name to the binary log:
set @asdfasdfasd = CURRENT_USER();
INSERT
Thank you for the reply.
well in essence the following is required.
we need to know who made what changes to tables.
we recently had a case of important data being deleted, however
finding it i binary logs proved 2 things :
1. it takes very long to find as we did not know in
2016/12/06 02:33 ... mach...@seworx.co.za:
The audit table should include the following information:
-- Who made the changes (username logged in)
-- What type of change (insert,update,delete)
-- Date of change including time.
-- if update, which fields
