On Aug 11, 2011, at 21:56, Andy Canfield wrote: > My goal in learning Subversion was to put our web site under version control. > Now I have my doubts as to whether Subversion can handle it. > > The web site uses Drupal. And Drupal has the characteristic that much of the > site is contained in a MySQL database. For example, if I install a module and > set it up, the module is a disk file, but the configuration of that module is > in the database. If I make a change, part of the change may be in a PHP code > file on disk, part may be in the database. The database contains both user > data and configuration data, intermingled. > > I could get Subversion to work. I would have a pre-commit script to back up > the database to a disk file in the working copy.
Not possible, because the working copy is on the client computer, whereas the pre-commit hook (and all hooks) run on the server computer. Unless you're saying you're working with a shared server-side working copy, in which case that's another thing I'd recommend not doing. > I would have a post-checkout script to reload the database from the disk file. There is no post-checkout hook, so this would have to be a script you run manually.
