add feature: INSERT INTO... SELECT ... #203
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
INSERT INTO... SELECT ...
. Different from another proposal, it uses more comfortable syntax (in my opinion), that isdbContext.DbSet.Insert(IQueryable)
.SqlBulkCopy
class. It must be much faster than executingDbSet.AddRange
method (or repetitiveDbSet.Add
method) and then executingdbContext.SaveChanges
method. The syntax isdbContext.DbSet.Insert(IEnumerable<Entity>)
QueryHelper
IBatchRunner
interface:Quote
method is to quote an identifier. The implementation for SQL server, the identifier will be enclosed by square bracket ([]), in MySQL will be by backtick (`), in Oracle should be by double quote (").DbNull
property returns null value for db command parameter. In SQL server, it returnsDBNull.Value
and in MySQL it returnnull
. This property is to avoid repetitive code when copying parameter fromObjectQuery
toDbCommand