Primary keys

[SebastianStehle]

No description provided.

[SebastianStehle]

This is a follow up after #19

I recommend not to have a look into it, until the other one is merged.

What I have done:

• Move stuff to the dialect (CreateTableCopySql) and create a method for that.
• Added another test.
• Move some stuff to the connection-info class to make the provider base easier.
• Improve performance of SQL building by using string builder properly and getting rid of string.Join to save allocations.
• Automatically use the primary key (when defined) for conflict detection, e.g. you can just do

await _context.ExecuteBulkInsertAsync(entities,
    onConflict: new OnConflictOptions<TestEntityWithGuidId>
    {
        Update = e => e,
    });

It only works with non-generated PKs, otherwise SQL server causes issues.

[SebastianStehle]

@PhenX Ready to be reviewed

[PhenX]

where is it used ?

[SebastianStehle]

Not anymore. I tested some stuff with SQL Server and whether it makes more sense to create the temp table manually.

The point is that the identity constraints are somehow copied to the SQL table, therefore you cannot make upserts when you have a auto-incremented ID. I still want to continue experimenting with that.

[SebastianStehle]

It is used now. I create the temp table manually for SQL server now, therefore you can make upserts with auto-incremented IDs now.

[SebastianStehle]

From my side it is ready to be merged.