Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If I understand correctly, you want to be able to track both schema and data changes.</p> <p>These are, in fact, two very different things - </p> <ul> <li><strong>Schema changes</strong> - this is discussed in several other questions (<a href="https://stackoverflow.com/questions/1294758/how-do-you-maintain-revision-control-of-your-database-structure">here</a>, <a href="https://stackoverflow.com/questions/308/is-there-a-version-control-system-for-database-structure-changes">here</a> and <a href="https://stackoverflow.com/questions/1607/mechanisms-for-tracking-db-schema-changes">here</a>). The main take from the answers to these questions is that you can either dump your schema to SQL files and track them with your regular source control (git, svn, etc.) or you can use a DB specific SW (red-gate, dbmaestro). However, this won't allow you to completely re-create an identical copy of a DB on another server. Which brings me to - </li> <li><strong>Data changes</strong> - This is harder, because (like @jonathan wrote) it's difficult track the changes the DB makes to it's files. I suggest you checkout <a href="http://off-scale.com" rel="nofollow noreferrer">OffScale DataGrove</a>. DataGrove tracks changes to the entire DB (structure+data). You can tag versions in any point in time, and return to older states of the DB with a simple command. It also allows you to create virtual, separate, copies of the same database so each team member can have his own separate DB. All the virtual copies are tracked into the same repository so it's super-easy to revert your DB to someone else's version (what you called "git-pull").</li> </ul> <p><em>Disclaimer - I work at OffScale :-)</em></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload