[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kmymoney4] [Bug 351511] erroneous change (matching?) of payees during QIF import from MS Money 97
From:       Thomas Baumgart <ipwizard () users ! sourceforge ! net>
Date:       2015-08-23 6:22:06
Message-ID: bug-351511-17878-pRZU2v5AGZ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=351511

--- Comment #6 from Thomas Baumgart <ipwizard@users.sourceforge.net> ---
@Allen: no, that option is only used during manual data entry

@Jack: no need for a regexp-wishlist entry - that is exactly how it is
implemented. And that is the cause of the problem here, as it does a partial
match. So in case you have an import into an empty file which contains 'Pool'
and 'Liverpool' as two payees, than it depends on the order in the QIF file if
you end up with one (order: Pool, Liverpool) or two payees (order: Liverpool,
Pool).

Changing the behavior so that "Match on Payee Name" requires a full match of
the string is easy to accomplish (source-code wise). If it is general consensus
that this is how the application should behave, than I go ahead and change it.

Here is a comment located at the automatic payee creation in
MyMoneyStatementReader:

        // for now, we just add the payee to the pool and turn
        // on simple name matching, so that future transactions
        // with the same name don't get here again.

Changing the "Match on Payee Name" to require a full match does not hurt here
at all and I don't see other cases where it would be a problem to change it. If
not wanted by the user, he can always change it to the "Match on a string in a
list" version, which supports both, partial and full, match versions out of the
box.

Comments?

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]