You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.
Modify DbSet to not use CommandGenerator directly, but only IQueryProvider.
CommandGenerator is class for creating commands for DbSet. But in case of database connection, it relies on IQueryProvider. IQueryProvider creates instance of DbCommand, because it knows database connection. Because of that, there is useless method GetCommandForCurrentTransaction.
It would be great if the DbSet will be dependent only on IQueryProvider and IQueryProvider will use CommandGenerator inside. Consider deleting CommandGenerator and moving code to IQueryProvider.
The text was updated successfully, but these errors were encountered:
Mikado3780
changed the title
Modify DbSet to not use CommandGenerator directly.
Modify DbSet to not use CommandGenerator directly
Apr 18, 2018
DbSet
to not useCommandGenerator
directly, but onlyIQueryProvider.
IQueryProvider
creates instance ofDbCommand,
because it knows database connection. Because of that, there is useless methodGetCommandForCurrentTransaction
.DbSet
will be dependent only onIQueryProvider
andIQueryProvider
will useCommandGenerator
inside. Consider deletingCommandGenerator
and moving code toIQueryProvider.
The text was updated successfully, but these errors were encountered: