Hi, > In the BIG db I have worked on there is a table that log every insert/update > on specific and important tables and a log of every sql statement execute > but I haven't ever see a db under version control with svn (or csv or git or > any other). > I'm (mis)using subversion more as a synchronization tool than as a version control system. I have a small software project and I have to work on this project on different computers (desktop, laptop, ...). To synchronize the project on all computers I use subversion. Before starting to work on one computer I make an "svn update" for the project and after finishing I do a "svn commit". This approach works quite well for my case, because in general only text files (source code, latex documentation,...) change. The problem with this project is that I shifted all the "content" (labels, translation etc.) from the source code into a small sqlite database. This clean separation of "logic" and "content" makes the update and modification of the project much easier. But the drawback is that the sqlite database is in a binary format and putting it into subversion is not optimal ;-).
A possible solution would be to export the sqlite database as a list of sql commands. This sql commands could be stored in a text file and be put under version control. Before starting to work on the project I could build from the text file the sqlite database. This approach means some extra work but in principle it should work. Are there any other solutions /approaches for sqlite available? Thanks Emal _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
