[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Patch for UPGRADE file
- Subject: Patch for UPGRADE file
- From: "David Bandel" <..hidden..>
- Date: Fri, 20 Apr 2007 08:24:54 -0500
A quick patch to add a few minor explanations to help out admins. Not
a big deal. I may start to work on an upgrade script if I have time.
David A. Bandel
Focus on the dream, not the competition.
- Nemesis Air Racing Team motto
--- UPGRADE.old 2007-04-20 07:51:44.000000000 -0500
+++ UPGRADE 2007-04-20 08:11:14.000000000 -0500
@@ -2,7 +2,7 @@
From LedgerSMB (1.1.1 or earlier)
-SQL-Ledger (2.6.19 or earlier)
+SQL-Ledger (2.6.27 or earlier)
This document contains information on how to upgrade from earlier versions of
LedgerSMB or SQL-Ledger. This upgrade is a major revision and may not go
@@ -58,10 +58,22 @@
d) Run the SQL upgrade scripts in order starting with the one whose name
begins with "Pg-upgrade-[version]" (each of these scripts will upgrade to
the next database version which is also identified in the file name).
-Note that this will create three tables that may not actually be used depending
-on your setup: users, users_conf, and session. In general if you have multiple
-datasets, these tables will only be used in one.
+ N.B.: use `ls -v` to see the scripts in version order and run them
+ in the order shown by this command.
+ e) If you have a problem running the scripts (errors due to ownership
+ or you just want to change ownership of the tables), connect to the
+ database as you did in c above and at the => prompt:
+ You will see a list of all tables, sequences, triggers, etc. After
+ creating a user (see the INSTALL file for details), you can change
+ ownership of the relation by running the following at the => prompt:
+ "ALTER TABLE|SEQUENCE|TRIGGER public.<relation_name> OWNER TO "new_owner";
+ Select the appropriate relation type and relation_name.
+ Rerun the upgrade scripts starting with the first one that failed.
+Note that subpara d above will create three tables that may not actually be
+used depending on your setup: users, users_conf, and session. In general if
+you have multiple datasets, these tables will only be used in one.
4) Decide where to put the user/session management tables. In general, we
recommend as follows: