MarkedMutantTbl

The lower 64bit of the checksum should be good enough as the primary key. By doing it this way it is easier to update a marked mutant without "peeking" in the database ("insert or update").

Both st_id and mut_id are values that sqlite can reuse between analyzes if they have been previously removed thus the only assured connection between a marked mutant and future code changes is the checksum.

Members

Variables

checksum0
long checksum0;

Checksum of the mutant status the marking is related to.

checksum1
long checksum1;
Undocumented in source.
column
uint column;
Undocumented in source.
line
uint line;
Undocumented in source.
mutText
string mutText;
Undocumented in source.
mutationId
long mutationId;

updated each analyze.

mutationStatusId
long mutationStatusId;

updated each analyze.

path
string path;
Undocumented in source.
rationale
string rationale;
Undocumented in source.
time
SysTime time;

Time when the mutant where marked.

toStatus
long toStatus;

The status it should always be changed to.

Meta