Percentage Similarity for Duplicate check

M

matsalim

Guest
How does this similarity percentage work during duplicate record check?

I come across one problem, I had a record with "Grove Ltd" in the company field which is set to check for duplicate during entry. Then I try to insert a new record with only "Grove" in the company field, and the record is successfully inserted. It totally by pass the similarity check.

Eugene, please explain.

Thanks.

 
E

Eugenio

Guest
matsalim wrote:

> How does this similarity percentage work during duplicate
> record check?
>
> I come across one problem, I had a record with "Grove Ltd" in
> the company field which is set to check for duplicate during
> entry. Then I try to insert a new record with only "Grove" in
> the company field, and the record is successfully inserted. It
> totally by pass the similarity check.

By default it is set to 80%, you can increase the percentage in config.php, even to 100%.

Eugenio.

(Latest version of DaDaBIK when this message was posted: 2.2.1)
 
M

matsalim

Guest
Both 80% and 100% did not prompt user, it did not check the similarity of "Grove Ltd" and "Grove".

 
E

Eugenio

Guest
matsalim wrote:

> Both 80% and 100% did not prompt user, it did not check the
> similarity of "Grove Ltd" and "Grove".

Probably you haven't set a primary key in your table, this is needed for the check similarity feature.

Eugenio.

(Latest version of DaDaBIK when this message was posted: 2.2.1)
 
M

matsalim

Guest
I did set a primary key "abID" in the table as below:

CREATE TABLE addressbook_tab (
abID int(11) NOT NULL auto_increment,
category varchar(100) NOT NULL default '',
main_contact varchar(255) NOT NULL default '',
company varchar(255) NOT NULL default '',
main_address varchar(255) NOT NULL default '',
state varchar(50) NOT NULL default '',
city varchar(100) NOT NULL default '',
zip varchar(100) NOT NULL default '',
country varchar(255) NOT NULL default '',
main_phone varchar(100) NOT NULL default '',
sec_phone varchar(100) NOT NULL default '',
main_fax varchar(100) NOT NULL default '',
sec_fax varchar(100) NOT NULL default '',
mobile varchar(40) NOT NULL default '',
main_email varchar(100) NOT NULL default '',
sec_email varchar(100) NOT NULL default '',
website varchar(255) NOT NULL default '',
notes longtext NOT NULL,
last_updated date NOT NULL default '0000-00-00',
designation varchar(50) NOT NULL default '',
supplier_code varchar(20) NOT NULL default '',
tsd_reg_no varchar(20) NOT NULL default '',
last_user text NOT NULL,
status text,
PRIMARY KEY (abID)
) TYPE=MyISAM;

I am not a programmer nor a database wizard, but DaDaBIK is very easy to understand and implement out of the box. Maybe you can highlight whats wrong to above table structure.

FYI: I've ported vAuthenticate 3.0 to implement user access and roles. Add a few conditional statement (if-else) lines in check_table.php file so that user belong to certain "team" and "level" can see the insert, delete and update icon whereas other user can only browse. I still learning PHP, so that I could make a better conditional statement or switch statement. Thanks to you Eugene.

 
E

Eugenio

Guest
matsalim wrote:

> I did set a primary key "abID" in the table as below:

[....]

You table structure seems ok.
Send me a dump of your database so that I can check the error.

Eugenio.

(Latest version of DaDaBIK when this message was posted: 2.2.1)
 
Top