Problem with protected InvFEST version

[cacereslab]

Apparently something happens with the protected InvFEST version once you log in.

• For many inversions (HsInv0006, hsInv0059,..) the frequency is not showing in the summary page, although it's present in the report.
• In HsInv0001 the manually curated BPs have dissapeared and the description has a strange string!

[RuthGG]

The history records show that the user InvFEST_engine, with date 2019-06-12 from 11:30 to 12:30 aprox. incorporated to the database multiple validations associated to HsInv0001 and HsInv0573, as well as several false papers (those that create the strange strings). I proceed with the deletion of this false data. Since this event happend in june, the backup files from july to october contain these errors, just in case we need to look at them again.

[RuthGG]

I put here the queries used to delete wrong data. they were automatically generated by MySQL Workbench.

Table researchs :

DELETE FROM `INVFEST-DB`.`researchs` WHERE `name`='!S!WCRTESTINPUT000001!E!';
DELETE FROM `INVFEST-DB`.`researchs` WHERE `name`='!S!WCRTESTINPUT000001<><>%3c%3e!E!';
DELETE FROM `INVFEST-DB`.`researchs` WHERE `name`='0';
DELETE FROM `INVFEST-DB`.`researchs` WHERE `name`='1';
DELETE FROM `INVFEST-DB`.`researchs` WHERE `name`='1 and 7=7';

Table breakpoints:

DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2658' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2657' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2656' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2655' and`inv_id`='232';
[...]
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2628' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2627' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2626' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2625' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2622' and`inv_id`='1';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2624' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2621' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2620' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2619' and`inv_id`='232';
[...]
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2573' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2572' and`inv_id`='232';
DELETE FROM `INVFEST-DB`.`breakpoints` WHERE `id`='2571' and`inv_id`='232';

From log_task:

DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149321';
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149322';
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149323';
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149324';
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149325';
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149326';

[...]
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149944';
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149945';
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149946';
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149947';
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149948';
DELETE FROM `INVFEST-DB`.`log_task` WHERE `id`='149949';

Due to foreign keys configuration, related entries were automatically deleted from tables validation and inversion_history.

[RuthGG]

Regarding the frequencies in the summary table, there was a backward compatibility problem: file search_invdb2.php, line 568, calls for the MySQL function inv_frequency, which has 5 input arguments instead of 4 since the metapopulation information was incorporated to the database, so I modified that line to provide the 5th argument.

Now more or less one third of validated inversions show their frequencies in the summary page, if that's correct the issue can be marked as solved.

[cacereslab]

Apparently the frequency of all the inversions is shown in the summary page. Thanks!