SQL transaction

[TomatorCZ]

Hi,

Is there a way how to make transaction processing in SQL ?
Is there a way how to skip failed rows which were failed and continue with inserting next rows ?

[paillave]

About the SQL transaction, you have to handle it on top of the ETL process. Nothing is planed for now to handle sub transaction within the process.

To skip failed rows, I can do something for this in a future release. You are working with entity framework extension or with direct sql extension?

Can you submit an example of your code for me to have a more precise idea of what you expect?

[TomatorCZ]

I already made it in a new operator.

Thanks

[paillave]

I already made it in a new operator.

Thanks

Ok good. Did you find the documentation clear enough for this purpose?

[TomatorCZ]

Yes. It took me some time to understand the architecture but after that the documentation was enough.
The architecture is very nice!

[TomatorCZ]

Can you execute the ExecuteNonQueryAsync in a transaction when it is provided by the database?

Reason

I try to execute the Delete(EFCore) operator within a transaction scope, but it throws an error, due to this command.
Setting its Transaction property based on the Database should fix this.

Etl.Net/src/Paillave.EntityFrameworkCoreExtension/Core/EfExtensions.cs

Line 61 in 698582b

var dbCommand = dbCtx.CreateCommand();

[paillave]

@TomatorCZ , I created an issue, I'll work on it asap.

[paillave]

@TomatorCZ Can you give me the exact exception stack you have?
Because according to me, any command running within the TransactionScope should run against it.

[TomatorCZ]

@paillave
I think that TransactionScope works fine when you have just one DbContext.

In a scenario, where you have multiple contexts and you want to perform something like distributed transaction, you cannot use this class yet in .NET Core(dotnet/runtime#715).
So I created two separate transactions and committed them at the end of the section. But this way of implementation requires additional treatment which I described above.

I hope it is helpful

[paillave]

@paillave I think that TransactionScope works fine when you have just one DbContext.

In a scenario, where you have multiple contexts and you want to perform something like distributed transaction, you cannot use this class yet in .NET Core(dotnet/runtime#715). So I created two separate transactions and committed them at the end of the section. But this way of implementation requires additional treatment which I described above.

I hope it is helpful

So (I reformulate to ensure I get it right) you mean you don't use distributed transaction as for now, EF Core can't handle it the way you want. Then you try to use a workaround to (somehow) simulate the distributed transaction behavior. This workaround is to make 2 ado.net transactions that you set to their respective context and that you manage manually. Am I right?

[TomatorCZ]

Yes, exactly.