[OPEN-ILS-GENERAL] Upgrade Script for 2.6.4 to 2.7

[Mike Rylander]

Chris,

That's what I've advocated for in the past (see upgrade scripts 0526 and
0537), via a helper script that 1) only applies what's needed (based on
config.upgrade_log) and 2) knows how to look up supersedes/deprecated-by
info from within the scripts.  Writing down a detailed plan keeps getting
back-burnered, but there are at least four different scripts floating
around that attempt to do various versions of that.

tl;dr of such a thing: all that's really needed to make that work is
 1) a concerted effort by devs to do things like supplying fine-grained db
scripts, particularly "reingest-only" scripts when a reingest is needed
 2) RM involvement in the creation of per-release scripts that do just
what's needed for the upgrade proper (like, do one and only one reingest)
 3) inclusion of supersedes/deprecated-by info in upgrade scripts that do,
in fact, supersede (or are deprecated by) early scripts
 4) a (say) perl script to read all the upgrade scripts and apply them in
order, as needed, based on config.upgrade_log



--
Mike Rylander
 | President
 | Equinox Software, Inc. / The Open Source Experts
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com


On Fri, Mar 13, 2015 at 3:47 PM, Chris Sharp <csharp at georgialibraries.org>
wrote:

> Since that's true...
>
> Couldn't we develop some sort of upgrade mechanism that just aggregates
> and runs each of the constituent scripts?  What is the reasoning behind
> stringing them into the longer monolithic scripts since running through the
> numbered scripts provides the same outcome?
>
> (Asking the full list, not Galen specifically).
>
> ----- Original Message -----
> > From: "Galen Charlton" <gmc at esilibrary.com>
> > To: "Evergreen Discussion Group" <
> open-ils-general at list.georgialibraries.org>
> > Sent: Friday, March 13, 2015 3:31:33 PM
> > Subject: Re: [OPEN-ILS-GENERAL] Upgrade Script for 2.6.4 to 2.7
> >
> > Hi,
> >
> > On Fri, Mar 13, 2015 at 1:51 PM, Lazar, Alexey Vladimirovich <
> > alexey.lazar at mnsu.edu> wrote:
> > >
> > > Since an Open-ILS/src/sql/Pg/version-upgrade script is a subset of
> several
> > > specific Open-ILS/src/sql/Pg/upgrade/XXXX scripts, is there any harm in
> > > just applying the XXXX scripts separately, in the order they appear,
> to get
> > > the database up to a certain “version" number?
> > >
> >
> > That approach will work just fine, though checking through all of the
> point
> > schema upgrades you plan to apply and seeing if there are any redundant
> bib
> > reingests that you can skip can save you some time.
> >
> > Regards,
> >
> > Galen
> > --
> > Galen Charlton
> > Infrastructure and Added Services Manager
> > Equinox Software, Inc. / The Open Source Experts
> > email:  gmc at esilibrary.com
> > direct: +1 770-709-5581
> > cell:   +1 404-984-4366
> > skype:  gmcharlt
> > web:    http://www.esilibrary.com/
> > Supporting Koha and Evergreen: http://koha-community.org &
> > http://evergreen-ils.org
> >
>
> --
> Chris Sharp
> PINES System Administrator
> Georgia Public Library Service
> 1800 Century Place, Suite 150
> Atlanta, Georgia 30345
> (404) 235-7147
> csharp at georgialibraries.org
> http://pines.georgialibraries.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20150313/a513662f/attachment.html>