LedgerSMB
The foundation for your business
Hi Erik, On Fri, Apr 17, 2020 at 07:56:30PM +0200, Erik Huelsmann wrote: > > The upgrade to 1.3.x is just a stepping stone to reach a supported > > version. I am going to have to go through a couple of iterations of > > upgrading LSMB then upgrading postgresql to inch my way up the ladder. > > > > If there's a better way, do please suggest it! > > > > Well, I'm short on time this weekend, but I've wanted to support migrations > from 1.2 to the current versions (1.6 / 1.7) out of the box. Not knowing > how many people are still on 1.2, at the time, it looked like a dumb goal > to give a high priority. However, if there are (many) others on this > mailing list on 1.2 as well, I'll be happy to work on that goal in the > short term! I don't suppose there will be many still using it. We are only still using it because the upgrades to 1.3 in the past were so problematic that it was always put off. Inertia can be a powerful thing. > I didn't know the answer to this: I hadn't seen CT_* before today. However, > I looked up the 1.2 code and searched for it. It's not in the code base. > It's in a few chart-of-accounts definition files, but that's all. I'm > thinking your data has a longer history than LedgerSMB 1.2 and that these > come from that line of history. Am I right? Yes, you are right. The data started off in SQL-Ledger and I *think* we moved to LedgerSMB at 1.1.x and then upgraded to 1.2.x but that's all so long ago that I cannot be sure. Digging through the existing 1.2.26 DB I have found the CT_tax references now. They are in the link field of the chart table for 3 VAT accounts. I expect that these can be ignored or even removed prior to running the upgrade. The problem with all these database errors is that they abort the transaction and therefore it is unclear to me whether the rest of the transaction would have been important or not. 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. I will persist. Pete -- Openstrike - improving business through open source https://www.openstrike.co.uk/ or call 01722 770036 _______________________________________________ users mailing list -- ..hidden.. To unsubscribe send an email to ..hidden..