summaryrefslogtreecommitdiff
path: root/UPGRADE
diff options
context:
space:
mode:
authoreinhverfr <einhverfr@4979c152-3d1c-0410-bac9-87ea11338e46>2007-05-07 06:02:55 +0000
committereinhverfr <einhverfr@4979c152-3d1c-0410-bac9-87ea11338e46>2007-05-07 06:02:55 +0000
commit19b819c58c2bd54d1354c8004e680a40e9ae94ec (patch)
tree3b3a561235193818dad05bfe928b70ea651a3050 /UPGRADE
parent1d4c913ccaf723b79d5a4dbd9fcbe9e4297ec9ad (diff)
Applying patch to bugs 1699718 and 1713439
git-svn-id: https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/trunk@1146 4979c152-3d1c-0410-bac9-87ea11338e46
Diffstat (limited to 'UPGRADE')
-rw-r--r--UPGRADE8
1 files changed, 6 insertions, 2 deletions
diff --git a/UPGRADE b/UPGRADE
index 1d7bcee6..db691f9d 100644
--- a/UPGRADE
+++ b/UPGRADE
@@ -53,8 +53,12 @@ and may not be required in all circumstances. These include:
a) cd to the sql/legacy/ directory of the new ledger directory
b) run "psql" with appropriate options to connect to your database.
- c) Note the db version by running the following query:
- "SELECT version FROM defaults;"
+ c) Note the db schema version by running the following query:
+ "SELECT value from defaults where setting_key = 'version';" (1.2.0 or
+ later)
+ or
+ "SELECT version FROM defaults;" (SQL-Ledger 2.6.x or LedgerSMB 1.1.x
+ or earlier)
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).