On Feb 15, 2013, at 11:13 AM, greg wrote: > Thanks! One followup, see below. > > -Greg > > On Fri, Feb 15, 2013 at 11:01 AM, Nate Coraor <n...@bx.psu.edu> wrote: >> On Feb 15, 2013, at 10:45 AM, greg wrote: >> >> >> Migrate: >> >> % sh manage_db.sh upgrade >> >> Pay attention to whatever the first revision you are migrating from is. >> Probably 109 if you were at the 1/13 release. > > Where would the "109" come from? How would I find my number?
Prior to running the database upgrade, you can use the `version` subcommand to determine your current database version: % sh manage_db.sh version 109 > >> >> If you need to downgrade: >> >> % sh manage_db.sh downgrade <old_db_version> >> % rm lib/galaxy/model/migrate/versions/*.pyc >> % hg update <old_changeset> > > What would I use for <old_db_version>? 109 in my example, it might be different for you if you're running an older version of Galaxy. --nate ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
