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" <[email protected]> > To: "Evergreen Discussion Group" <[email protected]> > 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 < > [email protected]> 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: [email protected] > 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 [email protected] http://pines.georgialibraries.org/
