From f106702d4447b0ee14043852aa3576f0c12e7fb8 Mon Sep 17 00:00:00 2001 From: Horst Schirmeier Date: Sat, 13 Jul 2013 13:05:39 +0200 Subject: [PATCH] prune-trace: remove pilot_id from fspgroup PK There's one fspgroup entry for every trace entry, the pilot_id is therefore *not* part of the (unique) primary key. If this had been right in the first place, it would have revealed an equivalence-based fault-space pruning bug early ... :-/ Change-Id: I449d4985645c6631c0a8db0c64510364677b1354 --- tools/prune-trace/Pruner.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/prune-trace/Pruner.cc b/tools/prune-trace/Pruner.cc index 1a8ad17e..9c981834 100644 --- a/tools/prune-trace/Pruner.cc +++ b/tools/prune-trace/Pruner.cc @@ -70,7 +70,7 @@ bool Pruner::create_database() { " data_address int(10) unsigned NOT NULL," " fspmethod_id int(11) NOT NULL," " pilot_id int(11) NOT NULL," - " PRIMARY KEY (variant_id, data_address, instr2, fspmethod_id, pilot_id)," + " PRIMARY KEY (variant_id, data_address, instr2, fspmethod_id)," " KEY joinresults (pilot_id,fspmethod_id)) engine=MyISAM"; return db->query(create_statement.c_str());