From: SourceForge.net <no...@so...> - 2011-05-12 02:37:34
|
Bugs item #3284494, was opened at 2011-04-11 10:17 Message generated for change (Comment added) made by sfrgpiel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1126676&aid=3284494&group_id=248804 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: ui Group: None >Status: Closed Priority: 8 Private: No Submitted By: William Piel (sfrgpiel) Assigned to: hshyket (hshyket) Summary: When too many trees are uploaded they cannot be deleted Initial Comment: Although the verbiage on our upload page (http://www.treebase.org/treebase-web/user/uploadFile.html) clearly states that submitters should limit the number of trees that they upload, they continue to ignore this warning. When 1000+ trees are uploaded the problem is twofold: (1) the user-experience is swamped by way too many trees for the same basic dataset, and (2) it is impossible to delete the trees, probably because of a database time-out. Let's implement two solutions: (1) only the first 30 trees from an incoming tree block will be parsed and stored -- the others ignored. (2) if possible, modify the delete-tree-block function (ie http://www.treebase.org/treebase-web/user/deleteATreeBlock.html?treeblockid=xyz) so that each time a tree inside this treeblock is deleted, the database does a commit. That way even if there is a time-out, the database won't completely rollback all the trees that were successfully deleted. ---------------------------------------------------------------------- >Comment By: William Piel (sfrgpiel) Date: 2011-05-11 22:37 Message: Let's just stick with solution (1), and then manually delete the existing uploads that have too many trees. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1126676&aid=3284494&group_id=248804 |