This one looks more like a problem the document delete API in general and not so much with how DW does it (which is pretty standard). i.e. it looks like a false positive warning to fix.
Apparently, the problem comes from the fact that the store delete API reload every single property before deleting it. Seems to me the only reason it does that is to make sure it does not try to delete a property that does not actually in the database, but. But reloading the entire property sounds like an expensive way to check if it exists... especially since delete won't fail if the property does not exist, and it seems the only use case for which we do this check.
Thomas Mortagne on 24/Jul/25 14:20
This one looks more like a problem the document delete API in general and not so much with how DW does it (which is pretty standard). i.e. it looks like a false positive warning to fix.
Apparently, the problem comes from the fact that the store delete API reload every single property before deleting it. Seems to me the only reason it does that is to make sure it does not try to delete a property that does not actually in the database. But reloading the entire property sounds like an expensive way to check if it exists... especially since delete won't fail if the property does not exist, and it seems to be the only use case for which we do this check.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
