QIF Importing skips transactions that match date & amount

[hsoft]

When importing using QIF files, if there are multiple transactions on the same date with the same amount, only the first gets imported. It does not seem to matter what other info is provided (e.g. description/payee). Of course, even if all the other details were identical, all records should still get imported.

I have attached a sample, hand-made QIF file to demonstrate the problem, based on the QIF data one of my banks produces.

The QIF contains 8 transactions that match the CSV below:

Date,Description,Amount,Balance
01/04/2012,"Transfer 1, Date 1, Amount 1",1.00,1001.00
01/04/2012,"Transfer 2, Date 1, Amount 1",1.00,1002.00
01/04/2012,"Transfer 3, Date 1, Amount 2",2.00,1004.00
02/04/2012,"Transfer 4, Date 2, Amount 1",1.00,1005.00
02/04/2012,"Transfer 5, Date 2, Amount 1",1.00,1006.00
02/04/2012,"Transfer 6, Date 2, Amount 2",2.00,1008.00
02/04/2012,"Transfer 7, Date 2, Amount 2",2.00,1010.00
02/04/2012,"Transfer 8, Date 2, Amount 3",3.00,1013.00

(I generated this to test if it was a general import bug or just QIF, and it seems to work fine with CSV so is probably just QIF).
(For what its worth I'm using dd/mm/yyyy dates, but I doubt that has any impact, other than needing to swap fields in the import wizard).

This bug is present on 2.5.2 and was present on the previous version too.
This only really affects one of my accounts (with regular transactions for the same amount), which I only started using QIF for at the start of the year so can't be sure how far back the bug might have existed.

[hsoft]

I can reproduce the bug. Thanks for reporting it.

[hsoft]

This bug was caused by the fix of #290. Darnit, QIF duplicate matching is quite a complex matter...

[hsoft]

(from [cf05c2f106cf]) [#323 state:fixed] Fixed a bug in QIF loading causing some false positives in duplicate transaction detection and removal.
https://bitbucket.org/hsoft/moneyguru/changeset/cf05c2f106cf/