The first is schema, the second is data (although in your question, you state data isn't something you're concerned about). If you want to manage change, in a database, you have 2 discrete problems, and I would address them separately (if I were you). The problem is normally git expects the context, on which it's generating delta's to be a file system, and similarly, when you checkout a point in the git hierarchy, it expects to generate a filesystem. The normal usage of git assumes that context is a filesystem, and those deltas are diff's in that file system, but really all git is, is a hierarchical database of deltas (hierarchical, because in most cases each delta is a commit with at least 1 parents, arranged in a tree).Īs long as you can generate a delta, in theory, git can store it. Git is a system, which in essence stores a database of deltas (differences), which can be reassembled, in order, to reproduce a context. The gist of the above answers, seem to similarly suggest an alternative solution to the problem asked, which kind of misses the point, of using Git to manage something in a Database, so I'll attempt to answer that question. It's distributed, across a cloud, using replication, hence it's access point will be via MySQL. I've come across this question, as I've got a similar problem, where something approximating a DB based Directory structure, stores 'files', and I need git to manage it. I don't really care much about the actual data. Such that when I switch branches, the database auto-magically becomes compatible with the branch I'm currently on. What I really want is not to track my development history, but to be able to switch from my "new radical changes" branch to the "current stable branch" and be able for instance to fix some bugs/issues, etc, with the current stable branch. Since this is only the development environment, I can choose whatever database I want. I'd like to put the entire database under version control, what database engine can I use so that I can put the actual database under version control instead of its dump? OK, so there' no better way, but I'm still not quite convinced, so I will change the question a bit: To be honest, I find that really hard to swallow. Someone suggested taking backups and putting the backup file under version control instead of the database. The database in my case is PostgreSQL Edit: I need to be sure, because these changes are not backward compatible I can't afford to screw up. How do I do that? is there a specific folder that I can keep under a git repository? How do I know which one? How can I be sure that I'm putting the right folder? I'm doing a web app, and I need to make a branch for some major changes, the thing is, these changes require changes to the database schema, so I'd like to put the entire database under git as well.
0 kommentar(er)
