[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: attempted upgrade from ledgersmb 1.2

After many iterations, I managed to upgrade from 1.2 to 1.3.
I have some minor patches/bugs to report, which I'll put on the devel
list.  The major bug is that I think that the upgrade process should
fail more clearly if the 1.2->1.3 transaction fails.

My database started in year 1999 with SL, and I now recall one time when
there was some corruption due to sequences that were reset.  I hacked
the database directly to fix it, and this was the major problem. 
I had to remove lines from my backup from acc_trans and invoice. 
I have the details, and I will need to check them.

My process was basically:

%less /tmp/ledgersmb/dblog_stderr                        
%sudo rm /tmp/ledgersmb/dblog_*
%vi 2011_12_29.sql
%ci -m'removed invoice: 11943' -l 2011_12_29.sql
%sudo -u postgres psql -f 2011_12_29.sql

REPEAT web interface attempt.
I used RCS to keep track of my changes, and I put a DROP DATABASE
statement and the \c sswbooks, at the top of my backup file.

My most immediate problem is that in cash reconciliation, it seems that
my banking account is not listed in the drop down for Accounts.  

How is that marked?

]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] ..hidden.. http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

Attachment: pgp8VEzrYF9hC.pgp
Description: PGP signature