Add function to allow batch inserts without transaction

Hello.

Currently, to do a batch insert you would use the Sql.executeTransactionAsync with a list of queries and parameters. However, this function starts and commits a transaction implicitly. Would it be possible to get a function that doesn’t implicitly create a transaction, allowing for separate control similar to this section in the readme. So essentially manually starting a transaction, then executing a list of queries with a single trip to the DB, and then manually committing/rolling back the transaction.

Thanks

[kaeedo]

@Zaid-Ajaj Sorry, maybe i should’ve explained my use case first. At my job, we’re making use of executeTransactionAsync to insert many items into the DB. However, now we have the need to manually either commit or rollback the transaction based on some other things happening shortly before or after the call to insert the items.

We can manually start a transaction, but then we can’t call executeTransactionAsync because it also starts a transaction internally, and postgres doesn’t support nested transactions (only savepoints)

What I propose is a new function executeManyAsync (or similar name) that takes a transaction as a parameter and hands that to use batch = new NpgsqlBatch(connection, transaction) instead of creating a transaction internally.

I’m willing to contribute a pull request if you’re happy with this addition

[pihai]

I agree with @kaeedo that the ability to execute commands in batch without implicitly opening a transaction would be a great addition.

We use the Unit of work pattern to manage our transactions. The repositories use Npgsql.FSharp to execute SQL commands. Currently we cannot use executeTransactionAsync to run multiple commands in batch because there is already a transaction open in the unit of work.

Even though our use case is to insert multiple rows in a batch, such API could also be used to execute multiple queries and read the results back. See the example here: https://www.npgsql.org/doc/performance.html#batchingpipelining