Save Database Field Changes - Best Practices? Versions, Loggable?

I am using Symfony 2 with Doctrine as an ORM Framework. I am looking for the best way to save changes made to database fields. I will have about 100 tables, each of which contains about 50 fields and several thousand rows. Now I would like to save all the changes made to the fields.

Features I was thinking about: Doctrine extension "Loggable" - saves the changes in another table, but does not know if it can afford this number of records.

MySQL Trigger for each table that saves changes to a new table?

But what is the best practice for saving change?

+5
source share
4 answers

MySQL, DoctrineExtension Loggable. , . MySQL (. mysql trigger FAQ).

:

  • ++,
  • ++ , script.
  • - - SQL ( ).
  • - PL/SQL, ,

:

  • ++ , .
  • ++ , API
  • - , .
  • - .

- , . , SQL .

+5

, , , , .

P.S. , MySQL, PostgreSQL , MySQL .

+1

" ". MySQL SO:

MySQL

, .

.

0

The following article provides a step-by-step explanation + sample version control execution code using triggers.

http://www.jasny.net/articles/versioning-mysql-data/

0
source

All Articles