I just posed this question to #subversion, with no reply. Any thoughts
I’m trying to decide how to manage database changes w/ subversion.
I’ve got a large number of production checkouts of a branch (actually,
multiple branches). Of course I have a base script to create the schema,
and this is updated of course when new fields are added to the system.
When a new field is added for a bug fix in a release branch, I need to
run alter scripts across all existing installs of the database.
Does anyone know known practices for managing these in the repository?
Rake migrate scripts? Etc? I’m trying to come up with a good schema to
keep track of which have been run on all live production servers, and
which still need to be run for a given revision in the repository.