The number of rows affected by a command is available via the return value of IDbCommand.ExecuteNonQuery, as well as via IDataReader.RecordsAffected. The only problem is that for command that contain multiple statements, this number is an aggregation and it's not possible to know the affect rows of each individual statement.
This is an important feature for EF7's command batching (dotnet/efcore#1956).
Add a new method on NpgsqlDataReader which exposes this information.
The number of rows affected by a command is available via the return value of IDbCommand.ExecuteNonQuery, as well as via IDataReader.RecordsAffected. The only problem is that for command that contain multiple statements, this number is an aggregation and it's not possible to know the affect rows of each individual statement.
This is an important feature for EF7's command batching (dotnet/efcore#1956).
Add a new method on NpgsqlDataReader which exposes this information.