server/UPGRADING.txt | 49 ---------- server/sqlobject-patches/sqlobject-sqlite-executescript.patch | 21 ---- 2 files changed, 70 deletions(-)
New commits: commit d4408b78a3b88ef78b81caf44d491027645b3f47 Author: Matt Domsch Matt_Domsch@dell.com Date: Wed Apr 27 11:28:05 2011 -0500
we don't need this sqlobject patch as we aren't using tg-admin upgrade anymore
diff --git a/server/sqlobject-patches/sqlobject-sqlite-executescript.patch b/server/sqlobject-patches/sqlobject-sqlite-executescript.patch deleted file mode 100644 index 05e2be6..0000000 --- a/server/sqlobject-patches/sqlobject-sqlite-executescript.patch +++ /dev/null @@ -1,21 +0,0 @@ -This patch allows multi-line SQL scripts, executed with tg-admin sql -upgrade, to complete if your backend database is sqlite. - -filed upstream as -http://sourceforge.net/tracker/?func=detail&aid=2883211&group_id=743... - - ---- sqlobject/sqlite/sqliteconnection.py.~1~ 2008-03-07 09:54:30.000000000 -0600 -+++ sqlobject/sqlite/sqliteconnection.py 2009-10-21 08:03:40.000000000 -0500 -@@ -172,7 +172,10 @@ - if self.debug: - self.printDebug(conn, query, 'QueryR') - try: -- return cursor.execute(query) -+ if query.count('\n') <= 1: -+ return cursor.execute(query) -+ else: -+ return cursor.executescript(query) - except self.module.OperationalError, e: - raise OperationalError(ErrorMessage(e)) - except self.module.IntegrityError, e:
commit fe3754a0a487d6719c7588e731ccd79acf9bf4b2 Author: Matt Domsch Matt_Domsch@dell.com Date: Wed Apr 27 11:26:07 2011 -0500
remove UPGRADING.txt - we have a new method now
diff --git a/server/UPGRADING.txt b/server/UPGRADING.txt deleted file mode 100644 index 3bf2825..0000000 --- a/server/UPGRADING.txt +++ /dev/null @@ -1,49 +0,0 @@ -On occasion, the schema of the MirrorManager database is updated to -add new functionality. As a mirrormanager administrator, you have -several choices to deal with this: - -1) drop all your existing tables and data, and start fresh with the -new schema. This erases all information in your database. You've -been warned. You can: - -$ tg-admin sql drop -$ tg-admin sql create - -2) upgrade your database's schema without destroying your data. -However, this requires that your database already has a table -sqlobject_db_version, which is created when running: - -$ tg-admin sql record --force-db-version=someversion - -This gets tricky, as the 'someversion' value isn't automatically -figured out - you have to specify it manually. If you look in -mirrormanager/sqlobject-history/, you see a bunch of directories -corresponding to the schema as it has changed over time. For example: - -mirrormanager/sqlobject-history/2009-02-23 -mirrormanager/sqlobject-history/2009-04-06 -mirrormanager/sqlobject-history/2009-10-21 - -In each directory you will find a file, mirrormanager_version.txt, -which shows the version of MirrorManager which first used this -schema. You need to force the database version once, like so: - -$ tg-admin sql record --force-db-version 2009-10-21 - -thereafter you can upgrade to the next version by doing: - -$ tg-admin sql upgrade - - -If you must upgrade across several versions, you have to use the ---upgrade-to argument, like so: - -# starting from 2009-02-23, 2009-10-21 is latest -$ tg-admin sql upgrade --upgrade-to=2009-04-06 -$ tg-admin sql upgrade --upgrade-to=2009-10-21 - -No, SQLObject doesn't make this easier. SQLAlchemy may. - -N.B. python-sqlobject-0.10.2 has a bug that is triggered on upgrade if -you are using a sqlite database. See the sqlobject-patches/ directory -for a patch to fix this.
mirrormanager-commits@lists.fedorahosted.org