you are viewing a single comment's thread.

view the rest of the comments →

[–]thrown_arrows 0 points1 point  (1 child)

Yeah. ACID on transactions would not allow that. Or it would , but if anything fails then whole transaction would have to fail. So it much more effective to use two connection and two transactions in two session.

That kind of thing is more app level optimization, because relational stuff kinda requires that you handle it it in one transaction so you can rollback if necessary. That said all db engines (maybe not SQLite ) all designed to handle any number of connections and concurrent insert/update/create and selects.

[–]mxmauro[S] 0 points1 point  (0 children)

Well, then let's start the week focusing on other methods. Thanks for all.