Frank Buckley

@halspang / @philliphoff - any update on this? it would be helpful. would you accept a PR?

> @frankbuckley What determines which configuration to use? For example, what determines which `ConfigurationName` is set when the object is resolved from D.I.? Can you show an example of the...

You could do this. I think there are good reasons for not configuring in `OnConfiguring`. You often want context (e.g. current environment) when configuring the app, and may want to...

> @frankbuckley Still not seeing it. Its fine to configure some things in `AddDbContext` _and_ others in `OnConfiguring` if needed. Yes, but that does not help the consumer (endpoint, handler,...

@ajcvickers You could do this – if (say) you wanted to apply a policy that all GET requests get a read-only context, but all POST requests get a read/write context...

To clarify, I am not suggesting that you “should allow users to just disable buffering” – existing behaviour with EnableRetryOnFailure and SqlServerRetryingExecutionStrategy would be preserved as today. You will not...

Thank you for considering. Is there anything that can be offered by contributors to help move #23721 and/or #30023 off the backlog?

We have seen some OOM exceptions in containers with memory limits that tend to be associated with executing a query that returns an `IAsyncEnumerable` over a sizeable resultset, which eventually...

Thanks for the quick reply! I agree – the option to avoid buffering by retrying the code block would be a good solution in many cases. However, if you are...

From what I can see, `RetriesOnFailure` is only ever used to configure `IsBuffering`, except for an error check in `ExecutionStrategy.OnFirstExecution()`, so if that is overridden to ensure the check is...