Hi,

On Thu, Jun 2, 2016 at 12:28 PM, Jesse McCarty <jes...@burlingtonwa.gov> wrote:
> Could simply running the 2.4.3-2.5.0-upgrade-db.sql prior to the current DB
> scripts work, or would only certain portions of that file need to be run? My
> test server is a VM with snapshots, so reverting and re-testing anything is
> trivial.

No, a subset should suffice.  Specifically, the following steps before
running the main upgrade SQL:

[1] running the SQL in upgrade/0795.schema.z39-batch-fetch-overlay.sql
(taken from the 2.10.x tarball)

For example:

psql> \set eg_version NULL
psql> \i upgrade/0795.schema.z39-batch-fetch-overlay.sql

[2] following up with just this bit from the 0843 upgrade:

ALTER TABLE config.z3950_index_field_map DROP CONSTRAINT
z3950_index_field_map_metabib_field_fkey;
ALTER TABLE config.z3950_index_field_map ADD CONSTRAINT
z3950_index_field_map_metabib_field_fkey FOREIGN KEY (metabib_field)
REFERENCES config.metabib_field(id) ON UPDATE CASCADE DEFERRABLE
INITIALLY DEFERRED;

Apropos of a conversation during the development meeting yesterday, DB
revisions 0841/0842/0843 are a good example of where backporting
schema updates can be tricky.

Regards,

Galen
-- 
Galen Charlton
Infrastructure and Added Services Manager
Equinox Software, Inc. / Open Your Library
email:  g...@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

Reply via email to