sql - Bending the rules of UNIQUE column SQLITE -

i working extensive amount of third party data. each data set has items unique identifiers. easy me utilise unique column in sqlite enforce data integrity.

out of thousands of records have id third party source matching 2 unique ids third party source b.

is there way of bending rules, , allowing duplicate entry in unique column? if not how should reorganise data take care of single edge case.

update:

create table "trainer" (   "id" integer primary key autoincrement,   "name" text not null,   "betfair_id" integer not null unique,   "racingpost_id" integer not null unique ); 

problem data:

miss beverley j thomas http://www.racingpost.com/horses/trainer_home.sd?trainer_id=20514

miss b j thomas http://www.racingpost.com/horses/trainer_home.sd?trainer_id=11096

vs. miss beverley j. thomas http://form.horseracing.betfair.com/form/trainer/1/00008861

both racingpost entires (my primary data source) match single betfair entry. 1 (so far) out of thousands of records.

if racingpost should have had 1 match error condition.

if racingpost allowed have 2 matches per id, must either have 2 ids, select one, or combine data.

since racingpost primary source, having 2 ids may make sense. if want improve upon data set combining data or selecting useful may more accurate. real question how data overlaps between these 2 records , when can detect reliably. if overlap small or have detection of overlap condition, combining makes more sense. if overlap large , cannot detect reliably, selecting recent updated or having 2 ids more useful.