I want to be able to track the data changes in the DB of my app so I’m thinking about storing, in a dedicated DB table, all INSERT, UPDATE and DELETE queries that my app executes.
Would that be a bad idea?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I want to be able to track the data changes in the DB of my app so I’m thinking about storing, in a dedicated DB table, all INSERT, UPDATE and DELETE queries that my app executes.
Would that be a bad idea?
We do that in debug mode – we output all the queries to a file. Of course, this does not make sense (and is a huge performance hit) on a production server, but we can turn it on there too, for short period of debugging.
Any way – mysql has query log you can turn on, it will record every single thing it does.