Using LLBLGenPro 4.2 with target LLBLGenPro framework using the Adapter pattern.

List<int> ids = requests.Select(r => r.RequestId).ToList();
                                RelationPredicateBucket relationship = new RelationPredicateBucket(RequestProcessingFields.RequestId == ids);
                                int result = adp.DeleteEntitiesDirectly(typeof(RequestProcessingEntity), relationship);

The ids list can often exceed 2100 parameters resulting in this exception:

An exception was caught during the execution of an action query: The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.

I found this setting on the Adapter - but this is defaulted to 50 and seems to control retrieval parameters as to when to use an IN statement over a subquery. ParameterisedPrefetchPathThreshold

What is the recommended approach? Should I just call the method with batches of say 100 ids until the list is exhausted?

Thank you.

ParameterisedPrefetchPathThreshold is for prefetchPath fetches only.

What is the recommended approach? Should I just call the method with batches of say 100 ids until the list is exhausted?

I'd recommend calling them in batches indeed, you can decide the size of the batches as performance dictates.

Please could you confirm if the Update/DeleteEntitiesDirectly methods are implicitly run as part of a transaction or do I need to create a transaction scope for these calls?

Thank you.

The statements themselves aren't wrapped in a transaction, as all other statements (except recursive saves), so an explicit transaction is needed for running all batches in 1 transaction