On 11/15/23 09:54, Shawn Heisey wrote:
If you change a DBQ to a multistep process where you first run the query to get the list of uniqueKey values, and then use that information to execute DeleteById updates, then the "interfering with ongoing indexing" that DBQ can cause will not happen.
The general problem with that is, of course, guaranteeing that the list won't change between the query and the last delete call.
IJS Dima
