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.
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.