BatchSaveChanges should support operation.AllowConcurrency = false about entityframework-extensions HOT 6 CLOSED

@JonathanMagnan I do not currently need this feature. BulkSaveChanges is enough for now. Feel free to close.

from entityframework-extensions.

Hello @jzabroski ,

After reviewing our code, it could be possible to skip the concurrency check. This means that in the case of a concurrency scenario, the entity will not be updated/deleted as of now but will not throw an error either.

However, we don't want to force the Delete or Update as the BatchSaveChanges currently don't touch the existing SQL generated by EF6; It simply batches all SQL in fewer commands.

If this solution is okay with you, I will ask my developer to look into it.

Best Regards,

Jon

from entityframework-extensions.

Hello @jzabroski,

Since our last conversation, we haven't heard from you.

Let me know if you need further assistance.

Best regards,

Jon

from entityframework-extensions.

Hey,

I would like this but I realized BulkSaveChanges works for me for now as I don't need additional indexes on this table. I plan to test BulkSaveChanges this week and revert back once I'm sure this works the way I want.

from entityframework-extensions.

Hello @jzabroski ,

Just to make sure, can we close this issue as you currently seem to not need the solution anymore from what I understand in your last message?

Best Regards,

Jon

from entityframework-extensions.

Ill confirm this week. Please keep open one more week.

from entityframework-extensions.