https://bugs.kde.org/show_bug.cgi?id=334995
--- Comment #8 from allan <[email protected]> --- On 23/05/14 23:37, Jack wrote: > https://bugs.kde.org/show_bug.cgi?id=334995 > > --- Comment #7 from Jack <[email protected]> --- >> No, I did mean 'or', but I over-simplified that and should have added 'and >> the other field is non-zero' > Why is that a problem? Sorry, why is what a problem? Here, the original problem was that the OP's file's transactions had a zero field and a non-zero field in every transaction. The plugin did not test for that and gave erroneous results. I had not encountered that situation previously. With CSV, there are no rules or official formats, at least so far as I am aware. It may be valid when importing into a spreadsheet, but not, in my opinion, when importing into the likes of KMM. Initially, I am issuing a warning to the user, and did not want to take responsibility for deleting/ignoring user's data without comment, but rather than warning for every single line, it might be better to warn that the zero fields are going to be dropped and giving the option to bail out. That apart, the only other problem is as you mention below, if both are non zero. That definitely is an error. If one is zero and the other is non-zero, then the > non-zero is the relevant field for that line. If both are zero then you can > use either one - isn't a zero deposit equivalent to a zero withdrawal? Isn't > the only error if both are non zero? > Allan -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ KMyMoney-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kmymoney-devel
