Bug 253493

Summary: Missing consistency check with database backend
Product: [Applications] kmymoney Reporter: Tony B <tonyb.sfkde>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED NOT A BUG    
Severity: wishlist CC: mfcarpino
Priority: LO    
Version: 4.5   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Tony B 2010-10-07 12:35:23 UTC 
Version:           4.5 (using KDE 4.4.4) 
OS:                Linux

When I save my data to a conventional (XML) file, a consistency check is performed. I don't seem to get this when I close a database backend file. Is this intentional?

Reproducible: Always
Comment 1 Alvaro Soliverez 2010-11-14 04:58:33 UTC 
Checks are performed on saving the file, which does not happen on the database. 

A check could be added before closing, if that is desired. But it is definitively not a bug, but a wishlist.
Comment 2 Tony B 2010-11-14 16:17:04 UTC 
That's very dogmatic. And what a strange thing to say, that saving doesn't happen on the database. Of course it gets saved, just as it goes along.

It's true that some of the checks made, e.g. duplicate ids, would not trigger due to being trapped by the DBMS. But there are others, the purpose of which is presumably to guard against discrepancies which may cause problems down the line. If it's considered desirable for users of conventional files, why should this protection not be provided to database users too?
Comment 3 Alvaro Soliverez 2010-11-14 17:12:46 UTC 
As I said, then it's a wishlist, as it was when we added it to file saving.

And yours to implement.
Comment 4 Michael Carpino 2018-03-01 15:40:25 UTC 
Bug requested over 5 years ago with an older version of KMM.  Bug closed.