Fix version numbers in 2.1 -> 2.2 upgrade script

Justin Hopkins spotted the problem, and offered a fix in LP #1015807.
I'm just doing it slightly differently here.  Thanks Justin!

Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>

diff --git a/Open-ILS/src/sql/Pg/version-upgrade/2.1-2.2-upgrade-db.sql b/Open-ILS/src/sql/Pg/version-upgrade/2.1-2.2-upgrade-db.sql
index a16a0cc..6ec712d 100644 (file)
--- a/Open-ILS/src/sql/Pg/version-upgrade/2.1-2.2-upgrade-db.sql
+++ b/Open-ILS/src/sql/Pg/version-upgrade/2.1-2.2-upgrade-db.sql
@@ -1,7 +1,7 @@
---Upgrade Script for 2.1 to 2.2-alpha2
+--Upgrade Script for 2.1 to 2.2.0
 
 -- Don't require use of -vegversion=something
-\set eg_version '''2.2'''
+\set eg_version '''2.2.0'''
 
 -- DROP objects that might have existed from a prior run of 0526
 -- Yes this is ironic.
@@ -11,7 +11,7 @@ DROP FUNCTION IF EXISTS evergreen.upgrade_list_applied_deprecates(TEXT);
 DROP FUNCTION IF EXISTS evergreen.upgrade_list_applied_supersedes(TEXT);
 
 BEGIN;
-INSERT INTO config.upgrade_log (version) VALUES ('2.2-beta2');
+INSERT INTO config.upgrade_log (version) VALUES ('2.2.0');
 
 INSERT INTO config.upgrade_log (version) VALUES ('0526'); --miker