wt.occurrence.StandardOccurrenceService.isUniqueOrDeleted() triggers the "select count(*) ..." SQL statement. Invoking the API in a loop will trigger a lot of "select count(*) ..." SQL statements in a short period. This results in the high DB CPU usage ratio and has the negative impact for the DB server.
Is it possible to not trigger the "select count(*) ..." SQL statement when invoking wt.occurrence.StandardOccurrenceService.isUniqueOrDeleted()?
We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.
You can always post a new idea with all the details required in the form.
Thank you for your participation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.