title: Versioning SQLite databases with Subversion. Good idea or bad idea?
body: <p>So I have a web system where every user gets a separate <a href="http://en.wikipedia.org/wiki/SQLite" rel="nofollow noreferrer">SQLite</a> database which acts as a sort of their workspace. All of the database files are in a directory with database names that match up to the user ids.</p>
  
  <p>Many of these databases are created and rarely, if ever, edited. Others have many edits on a daily basis.</p>
  
  <p>To manage backups on this directory would you recommend using <a href="http://en.wikipedia.org/wiki/Subversion_%28software%29" rel="nofollow noreferrer">Subversion</a> set up with a <a href="http://en.wikipedia.org/wiki/Cron" rel="nofollow noreferrer">cron</a> process? One reason I am considering this approach is it would allow for the users to roll back their edited workspace easily.</p>