*** empty log message ***

misc-scripts/README.schema_patching

+Schema patching using patch_schema.pl
+=====================================
+
+
+Schema patches are split into multiple files, each containing one
+"task". The convention for patch files (in ensembl/sql) is:
+
+    patch_FROM_TO_[a-z].sql
+
+where FROM is the schema version before patching, TO the version to
+patch to, and [a-z] is a letter specifying the respective patch.
+
+each patch will put an entry into the meta table (meta_key = 'patch') to
+indicate that it has been applied successfully. this should make it
+easier to track which patches have been applied to which dbs.
+
+this meta information is also used by the new script to determine which
+patches need to be applied to a db (note that you can still apply the
+patches manually if you prefer). the script is
+ensembl/misc-scripts/schema_patch.pl, run with --help to see all options
+it accepts (on the commandline or from an ini-style script passed in
+with --conffile).
+
+Your usual procedure as a release coordinator would probably be:
+
+1. check which patches need to be applied:
+
+this step is entirely optional, you can proceed to step (2) immediately
+if you like.
+
+    $ ensembl/misc-scripts/schema_patch.pl --host ecs2 --port 3364 \
+        --user ensadmin --pass ensembl --pattern %_core_39_% --schema 39 \
+        --dry_run 1 --interactive 0
+
+2. actually patch the databases:
+
+    $ ensembl/misc-scripts/schema_patch.pl --host ecs2 --port 3364 \
+        --user ensadmin --pass ensembl --pattern %_core_39_% --schema 39 \
+        --logfile /your/log/patch/schema_patch.39.log
+
+the script will run interactively and prompt you for each database
+matching the pattern. --logfile is optional but useful for keeping track
+of what you've done.