-
Notifications
You must be signed in to change notification settings - Fork 256
Description
#2400 added a UseNpgsql overload which accepts a built DbDataSource, but that requires users to do the building outside the EF call, get a data source, and pass that in. This isn't a great experience.
Experiment with having a UseNpgsql overload which accepts an NpgsqlDataSourceBuilder lambda, allowing configuring the data source in-place. The potential problem is the Intellisense ambiguity with the overload accepting a DbContextOptionsBuilder lambda.
Another advantage of a NpgsqlDataSourceBuilder lambda is that EF plugins (NodaTime, NTS) would be able to apply ADO-level mapping plugins to the data source builder before the data source is built, at least in theory. That would provide a seamless experience where you just add NTS at the EF level, and don't have to worry about the ADO.NET/data source level.