Move PLPERL dropping outside of 2.1-2.2 upgrade transaction
authorDan Scott <dan@coffeecode.net>
Fri, 11 May 2012 14:45:39 +0000 (10:45 -0400)
committerLebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Fri, 11 May 2012 20:03:09 +0000 (16:03 -0400)
commit0c04d111f824fc6ddb936982072b303d3899ec63
tree5c232085c1cd792285529a2e0f45ad0008c6f14f
parent6238c9e0cbdd778c5a6944023d0ab305ccc77a01
Move PLPERL dropping outside of 2.1-2.2 upgrade transaction

Sites might have added custom PLPERL database functions for migrations,
data clean up, etc, so don't make the success of the 2.1-2.2 upgrade
hinge on a database schema that exactly matches vanilla Evergreen;
just move it outside of the upgrade transaction and output a reassuring
note.

Signed-off-by: Dan Scott <dan@coffeecode.net>
Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Open-ILS/src/sql/Pg/version-upgrade/2.1-2.2-upgrade-db.sql