On Sun, Apr 19, 2020 at 1:28 AM Erik Huelsmann <ehuels(a)gmail.com> wrote:
Something is clearly
going wrong with the upgrade as a whole as, for
example, the ap table
is completely empty after the upgrade. There are 185 errors listed in
the db log file and trying to guess which ones are relevant makes the
whole thing more difficult.
Feel free to send me the dump with errors [off-list] (and the file you're
running which is causing them). I'll have a look and see if I can help you
based on that.
Just to confirm: off-list, Pete and I are working on getting his company
migrated. The results of the efforts are being taken back into the code
base of the project. One of the results is a major refactoring of the
upgrade process (the code) in setup.pl; the new way of coding highlighted
discrepancies between upgrades from LedgerSMB 1.2 and SQL Ledger 2.8 and
3.0 -- a very nice result. Another result is that the upgrade code in 1.7
had a number of issues which break migration full stop. For 1.8, those will
-- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.