[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Locking Last Cost
- Subject: Re: Locking Last Cost
- From: Joseph <..hidden..>
- Date: Tue, 29 Sep 2009 22:55:23 -0600
On 09/29/09 21:05, Chris Travers wrote:
On Tue, Sep 29, 2009 at 7:52 PM, Joseph <..hidden..> wrote:
I've jumped from SQL-Ledger 2.2.7 to 2.6.27 in hope that I would be able to
use most stable version 1.2.9 but uploading the sql-ledger database to
is not the way to go I think as I got a lot of error messages and could no
longer long in into ledgersmb.
So, I deleted the database and reloaded a new one.
I've notice that Ledgersmb does not change the last cost in the database
upon ordering or changing the exchange rate, that is good.
How to do upgrade?
The upgrade scripts are in /sql/legacy/ in the LedgerSMB directory.
Before you begin: select version from defaults;
Then start with that version (Pg-upgrade-2.6.14-2.6.18.sql for example) and
run each script in sequence until you run out of them. This will bring it
up to speed. If a script errors out, ask for help here on this list.
Thanks for the input.
So to be clear, I create an empty database load my sql-ledger data into it and start the upgrades, from my version forward, isn't it?
These numbers are a bit confusing :-)
My current version SQL-Ledger is 2.6.27 but when I save a backup it saves file as 2.6.12; so I should start loading the changes from 2.6.12 ?
psql -U user my database < Pg-upgrade-2.6.12-2.6.17.sql
So the last two files are:
What database version is LedgerSMB using?
When I try to save it to a file it is showing 1.2.0
So I'm lost a bit where to start and where to finish?