https://bugs.kde.org/show_bug.cgi?id=334995
Jack <ostrof...@users.sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ostroffjh@users.sourceforge
| |.net
--- Comment #9 from Jack <ostrof...@users.sourceforge.net> ---
I think this may just be a difference of degree. I agree with the importance
of data integrity, but given the assumption (I think we agree) that each row
represents either a debit or a credit but not both at once, then if it uses
separate columns for debits and credits, it seems that having a non-zero debit
OR credit with the other zero is exactly what SHOULD be expected. Perhaps
missing or blank would be better, but I don't see this as ignoring the zero, if
it can't be any non-zero value without being an error. I certainly agree with
a warning the first time this happens, strongly suggesting that the user
carefully confirm that the results of the import are what are expected. Giving
the option to bail out is good, but so is the option to continue, especially
if this is what the user actually expects, I guess the problem is that we are
overly sensitive to the potential bad things that can happen when we make any
assumptions that might not match the user's reality. Notices and warnings are
good, as long as they don't prevent the user from doing what he/she wants to
do.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
