How to prefix an update statement with a SET, whilst maintaining DbConcurrencyException logic about efcore.pg

[mattbdc]

I guess I need this to start at 1 somehow
NpgsqlModificationCommandBatch

efcore.pg/src/EFCore.PG/Update/Internal/NpgsqlModificationCommandBatch.cs

Line 84 in 6b3ca68

var commandIndex = 0;

[mattbdc]

So it's possible with providing your own NpgsqlModificationCommandBatchFactory and return a version of NpgsqlModificationCommandBatch that works out reader.Statements - ModificationCommands.Count are prefix commands then npgsqlReader.Statements[commandIndex + numberOfPrefixCommands].Rows !=1 but I think I'm just going to take the pain of round tripping a select set_config at the start of begin transaction as completely seperate command.

This got ugly, complicated, and yeah overkill quickly whoops. This can be closed if on same page.

[roji]

There's unfortunately no good way to do this currently, without hacking around with internal types etc... One way to address this would be npgsql/npgsql#4522, which would allow prepending SQL at the lower-level Npgsql level. This has come up before.

For now, if you're not too concerned about the perf overhead of performing another database roundtrip, it's true that that's probably the simplest way.

I'll go ahead and close this as I don't really see a solution inside EF or EFCore.PG itself... But of course feel free to post back here and we can continue the conversation.