When using the option to delete when loading a GFF3 file any features that do not have a unique ID specified in the GFF file will not be deleted. This is because the loader can't find them because their unique ID's were autogenerated and include the date. It's not possible to recreate that uniquename accurately because we don't know the original date the GFF was loaded. This would require that we get a bit tricky in the code to try and find children, or use a like operator to avoid the date. But any of these cannot guarantee that we are deleting the correct record. Also, what if the GFF3 file was loaded using the Perl loader? The solution may be to just remove the option to delete records using the GFF3 loader, and suggest users use the feature delete page that comes with tripal_feature administrative pages.

Comments

spficklin’s picture

Status: Active » Fixed

As a short-term solution, I'm commenting out the ability to delete features using the GFF loader, If no one complains we can later remove it entirely.

spficklin’s picture

Status: Fixed » Closed (fixed)