[Pkg-sql-ledger-discussion] Bug#675816: ledgersmb: Unable to upgrade from 1.2 db to 1.3 db
Robert James Clay
jame at rocasa.us
Sat Jun 9 14:05:31 UTC 2012
Forwarding as info to the bug:
On Fri, 2012-06-08 at 22:24 -0400, Chris Travers wrote to Robert James
Clay in the Ledger-smb-users mailing list:
> On Fri, Jun 8, 2012 at 7:09 PM, Robert James Clay <jame at rocasa.us> wrote:
> > On Fri, 2012-06-08 at 21:36 -0400, Chris Travers wrote:
> >> If it were me I would try this (on a copy of the data of course):
> >> I would comment out the check constraint on line 483 of the
> >> Pg-Database.sql and try again.
> >
> > Simply try the conversion again? The import? (I.E.; when does that
> > sql get used; any time a database gets created, including during a
> > conversion? Or does it get loaded into Pg and then used from there?)
>
> The conversion operates in a few stages:
>
> 1) Checks 1.2 data
> 2) Moves the public schema to lsmb12. Creates new public schema,
> loads with Pg-database etc.
> 3) Copies data from lsmb12 into public schema.
>
> The big advantage here is that it's possible to back out from a broken
> upgrade and get to exactly where you were after step 1.
More information about the Pkg-sql-ledger-discussion
mailing list