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:02:07 +0000 (16:02 -0400)
commitbcb1c10f2cde5c812f47da557c2dddc9fda2e0ab
treeb0f0ce25bf5eec69be29aa509bcaad5a183ab864
parent8f95eaeaf0bbc03be7c5e017d574234315eee97d
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