Bug 204095 - It is possible to create the same contact twice or to import it twice in the same folder.
Summary: It is possible to create the same contact twice or to import it twice in the ...
Status: CLOSED NOT A BUG
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-16 22:57 UTC by Sabine Faure
Modified: 2009-08-26 22:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sabine Faure 2009-08-16 22:57:38 UTC
Version:            (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

- Launch KAddressBook.
- Go to File/Import/Import CSV file...
- Select a CSV file containing a few contacts to import and rename the column titles from 'Undefined' to whatever it should be (ex: formatted name, Home Phone...).
- Click on the 'ok' button.
- Select a folder in KAddressBook

The contacts are successfully imported (only the Note field is lost somehow. I'll retest this and report another bug about it if needed).

- Redo the same action as above once more and select the same folder.

The exact same contacts are imported again and appear on the list of contacts

Note: it is also possible to create an identical contact twice from the 'New Contact' button.

SVN REV 1011519
Comment 1 Tobias Koenig 2009-08-17 10:22:58 UTC
Hej Sabine,

KAddressBook does not intent to disallow the user to create the same contact
twice since it is techincally not 100% possible to detect whether a contact is
equal to another contact. If the user wants to have it twice in its address book,
why not? In a later version KAddressBook will however provide functionality to
merge multiple contacts into one.

Ciao,
Tobias
Comment 2 Sabine Faure 2009-08-26 22:49:49 UTC
Ok. I did not know that it was intended.
I am verifying this bug then.

Trunk, Svn Rev 1015767