Hi,
What about upgrades from 1.0 series to 1.2? Are they supported and
working? I just upgraded from sql-ledger to ledger-smb, but used the
1.0 series to do the upgrade. I'd like to jump into the newest series
if possible :)
Thanks,
MG
On 02/03/07, Chris Travers <..hidden..> wrote:
> The upgrade to 1.2 will not be as smooth as past updates becuase we
> have opted to make a number of fixes that break the automatic update
> system. The main ones are a change to the defaults table structure
> and a deep change in how user info is stored.
>
> Yes, there is an upgrade path, but it is not as simple as it has been
> with past versions because we decided that some problems needed to be
> truly fixed.
>
> Best WIshes,
> Chris Travers
>
> On 3/2/07, Doug Poland <..hidden..> wrote:
> >
> > On Thu, Mar 01, 2007 at 10:37:43AM -0800, Chris Travers wrote:
> > > Doug Poland said:
> > >>
> > >> I've been using SQL-Ledger for about a year and am currently
> > >> running 2.6.16 on PostgreSQL 8.1.4 to manage my small IT consulting
> > >> biz. As I've fallen several rev's behind SL, I'm considering
> > >> making the leap to LedgerSMB instead of the latest SL.
> > >>
> > >> My question is, how far can I "fall behind" LSMB before a migration
> > >> from SL 2.6.16 to LSBM is impossible or very *painful*?
> > >>
> > >
> > > The migration to 1.1.8 is designed to be no more painless than an
> > > upgrade of SQL-Ledger. 1.2 will be harder and we are working on
> > > migration issues at the moment.
> > >
> > Since I'm not in a big hurry to upgrade, would you say that I'll have
> > and upgrade path after 1.2 is released? As I am an Open Source
> > programmer/network admin, I'm capable and not afraid of rolling up my
> > sleeves. That said, this is one app I don't get paid to drive and
> > like it when it *just works*.
> >
> > > There are two corner cases where you can run into problems, however:
> > >
> > > 1) If you have custom views, the change from DOUBLE to NUMERIC may
> > > cause the upgrade to fail. You will probably want to drop the views
> > > first, then recreate them later. pg_dump can be used to dump view
> > > definitions.
> > >
> > I didn't do any customizing
> >
> > > 2) We are a lot more strict regarding data integrity than
> > > SQL-Ledger. There are a number of situations where data corruption in
> > > SQL-Ledger is allowed to slide and in these cases, the upgrade will
> > > fail. We can help you resolve these issues, however.
> > >
> > Thats hard for me to know and will cross that bridge if necessary :(
> >
> > > My recommendation is to create a copy of your database and use that
> > > for the upgrade. Something like createdb -T sql-ledger ledger-smb
> > > will create a new database named ledger-smb as a copy of sql-ledger.
> > > Of course having other backups is a good idea for reasons other than
> > > the upgrade.
> > >
> > I don't do *anything* in SL without backups :) Thanks for your advice!
> >
> > --
> > Regards,
> > Doug
> >
> >
> >
> > --
> > Regards,
> > Doug
> >
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys-and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Ledger-smb-users mailing list
> > ..hidden..
> > https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
> >
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Ledger-smb-users mailing list
> ..hidden..
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
>