.NET Data Community Standup - DbDataSource, a new System.Data abstraction

In this episode of the .NET data community standup, we'll explore DbDataSource, a new abstraction being introduced to System.Data in .NET 7.0. DbDataSource unlocks easier integration of ADO.NET drivers with dependency injection, better management of advanced driver configuration, helps performance and more. Tune in to see improvements at the lower levels of the .NET data stack.



​

#dotnet #data

[johnnyirish]

Fantastic session as always!! Love to see this great integration. Please also give this kind of love to other providers as well.
If the multi replica support could also somehow make it to ef core, where we then could get readonly or readwrite contexts depending on what we want to do, that would be fanatstic as well.

[jfras]

I would like to see a Community standup on EFCore Sqlite provider. See more information on using DI and use of DbContext factory.

[solidsloth]

Thanks, Shay. I never knew PG had a convention that the assumed DB matched the username, and the majority of the time mine do...🤦

[amitsinghrawat]

What is the best way to do a migration in dotnet 6?

[alexisfibonacci]

Mark Pflug asked this question in the live chat, I am not sure if it was answered:

Can DbDataSource provide a unified API over bulk load API? The SqlClient and Npgsql APIs are quite different, but it looks like they could be adapted to a unified abstract API.

[Eirenarch]

Seems to me that Shay is wrong about the lifetime of the connection. He registers it as transient and claims it will be disposed (it will be disposed by the GC but not otherwise) and also claims that the helper method will add it as transient and if you pause the video it clearly says it registers it as scoped by default

[DickBakerSql]

What about connection retries as part of such "ready to use" connection? Ditto there have been several implementations over the years within ADC/ADO/ADO.NET/ODBC & MSSQL primary/secondary alts and POLLY especially for resiliency [commands]; surely something that should be built-in [as cross-cut concern] to save every dev having to even think about it. Not saying have to blindly forego to f/w for retries as an app may want to hook into an OnLost/OnError interception (to notify UX that there is a problem brewing "do not adjust your set, normal service will resume shortly") but imho should be avail as an opt-in.