On Thu, Jan 27, 2011 at 1:44 PM, Dan Scott <[email protected]> wrote: > On Thu, Jan 27, 2011 at 12:24:47PM -0500, Jason Stephenson wrote: > > <snip> > >> When you install Evergreen from a tarball (a .tar.gz file), the >> config.upgrade_log is not currently set with the latest database >> version number in the same way that it is set from a SVN checkout. >> This means that there is no easy way to upgrade your database >> without running eg_db_config.pl and recreating the schemas thereby >> losing all of your data. > > D'oh! This is the part where I eat crow; I didn't realize the > config.upgrade_log insert statement was getting munged in the tarballs > to an effectively useless value. Perhaps we should be inserting both the > real version number ('0478' for 2.0.0) as well as the human-readable > value ('2.0.0') so that the upgrade scripts still could be used. >
Pass me some of that bird, because that's my fault. I will add instead of replace from now on. -- Mike Rylander | VP, Research and Design | Equinox Software, Inc. / The Evergreen Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com
