Re: upgrade from 1.2.21 to 1.3.3

[Alvin Starr <..hidden..>]

I have an old database also and I don't think there would have been an 
automated fix.

I wonder if it would make sense to have 1.2.2x have a upgrade vailidity 
check.
Where you could run the check then go fix the problems then re-run the 
check.

When i was doing the fixes I was running the checks on a 1.3 test system 
then going to my live system fixing the problems and copying over the 
database and checking again.


On 11/04/2011 10:46 AM, David A. Bandel wrote:
> On Fri, Nov 4, 2011 at 09:40, Alvin Starr<..hidden..>  wrote:
> >   I have seen this page.
> > It is the result  from the pre-upgrade tests failing.
> Actually, the latest setup.pl (upgrade script) does bail with a more
> descriptive error message if the pre-up tests fail.  It doesn't
> actually fix those errors.  I have a _very_ old database that needed
> significant repairs (I had orphans and non-unique values in columns
> that are, and always should have been, unique, and more).  Fixing an
> old database is very problematic, and must be done by hand.
> Automating this could cause more problems than it solves.
>
> > I think an argument could be made that the failure could be a little
> > more descriptive and suggest where to look for how to fix things.
> well, in some cases, that's done.
>
> > On 11/04/2011 09:50 AM, Philippe Schelté wrote:
> > > Hello Chris,
> > >
> > > thanks for your reply !
> > >
> > > > Use the setup.pl.
> > > >
> > > > Enter the company and postgresql superuser/password authentication
> > > > fields.  The company is your database name.
> > > >
> > > > It should detect 1.2 and ask if you want to upgrade.  Say yes and
> > > > continue.....
> > > I have done the setup.pl as I explain in my first message in this
> > > thread :
> > >
> > > I choose to upgrade my database, but it seems that i can't go
> > > further, I 'm blocked on a step where it asks me to "save and retry"
> > > showing me a form
> > > where I see all the parts with only the partnumber column that I can
> > > modify. Even if I put all the partnumber to 1 and click to "Save and
> > > retry" the form reload
> > > again and so forth... Something I have to mention is that I'm a french
> > > user and some of my parts description have accent that are not well
> > > encoded.
> > > I have strange characters like "@A" at the place of the accents. How
> > > can I finish the upgrade process ?
> > >
> > > Best regards
> > >
> > > Philippe
> >
> > --
> > Alvin Starr                   ||   voice: (416)585-9971x690
> > Interlink Connectivity        ||   fax:   (416)585-9974
> > ..hidden..              ||
> >
> >
> > ------------------------------------------------------------------------------
> > RSA(R) Conference 2012
> > Save $700 by Nov 18
> > Register now
> > http://p.sf.net/sfu/rsa-sfdev2dev1
> > _______________________________________________
> > Ledger-smb-users mailing list
> > ..hidden..
> > https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
>
> David-


--
Alvin Starr                   ||   voice: (416)585-9971x690
Interlink Connectivity        ||   fax:   (416)585-9974
..hidden..              ||