consistency check showing lots of NEW errors after saving file with new version

[Jack]

On 2025.01.22 03:57, Thomas Baumgart via KMyMoney-devel wrote:
> On Mittwoch, 22. Januar 2025 07:11:54 CET Ralf Habacker via  
> KMyMoney-devel wrote:
> 
> > Hi Jack,
> >
> > Am 22.01.25 um 02:12 schrieb Jack via KMyMoney-devel:
> > > I just compiled a fresh version, and the first time I saved, the
> > > consistency check came up with over 4000 problems.  ALL are in
> > > investment accounts, several of which have been closed for many
> > > years.  I suspect it's an unintended side effect of the recent  
> work on
> > > storing prices for add/remove share transactions.
> >
> > with https://invent.kde.org/office/kmymoney/-/merge_requests/257 the
> > previously broken ‘fix version’ support was repaired. I suspect  
> that one
> > of the existing fixFile_x functions with x < 5 is responsible for  
> this.
> > To find this, you can modify your kmymoney file in xml format by  
> first
> > setting the <FIXVERSION id=‘x’/> entry to x = 4, loading this file  
> and
> > then running the consistency check. If no problems occur, decrement  
> x
> > and repeat the whole process until the errors occur.
> 
> I added https://invent.kde.org/office/kmymoney/-/commit/94519cbe to
> cope with the transition scenarios.

I finally have time to dig into this, but with both suggestions, it is  
not clear whether I need to use the latest data version prior to the  
problem, or the newest version.  Will my following Ralf's suggestion  
provide any helpful information, or does Thomas' commit make that  
unnecessary?

I've determined that there are only twelve new transactions, so in  
terms of recovery, I could just run KMM separately on each file (latest  
and latest prior to problem) and re-add those transactions in the known  
good file.

Jack