transactions

问题 I'm examining the MS SQL Transaction Log for investigating a problem, and found there are a huge amount of LOP_INSERT_ROWS and LOP_DELETE_ROWS operations on a SQL View object within a single "user_transaction" last for over a minute. I just curious what is the meaning of a LOP_INSERT_ROWS and LOP_DELETE_ROWS operation on a View object? Do they mean the action on creating and dropping a View object? Thanks. [Updated on 2016-05-12] The following is the user_transaction (0000:0f20ab9b) I

问题 How can I force a transaction commit in Spring Boot (with Spring Data) while running a method and not after the method ? I've read here that it should be possible with @Transactional(propagation = Propagation.REQUIRES_NEW) in another class but doesn't work for me. Any hints? I'm using Spring Boot v1.5.2.RELEASE. @RunWith(SpringRunner.class) @SpringBootTest public class CommitTest { @Autowired TestRepo repo; @Transactional @Commit @Test public void testCommit() { repo.createPerson(); System

问题 I am using SqlTransaction s in my code for roll back purpose. Within the transaction I got multiple statements to be executed with may include selects inserts and updates. All these statements are within the scope of the sqltransaction . Everything works fine just for one problem. I am using datareader s for select statements . And these readers are closed once they are used. This forces the connection to be lost and every thing fails. Does any one have a solution on whether I can use

问题 I am using SqlTransaction s in my code for roll back purpose. Within the transaction I got multiple statements to be executed with may include selects inserts and updates. All these statements are within the scope of the sqltransaction . Everything works fine just for one problem. I am using datareader s for select statements . And these readers are closed once they are used. This forces the connection to be lost and every thing fails. Does any one have a solution on whether I can use

问题 All MyService methods are transactional. The junit test below, gets count of items, saves a new item, and gets count of items to make sure that counts has been incremented by 1. public class MyTest extends ServiceTest{ 1. int countBefore = myService.getCount(); //return n 2. myService.add(item); //item is really added to DB 3. int countAfter = myService.getCount(); //return n (sometimes n+1) } @Transactional(propagation=Propagation.REQUIRES_NEW, isolation=Isolation.READ_COMMITTED) getCount(){

问题 With the last version of Kafka 0.11.0.0 the Apache team is introducing idempotent producer and transactions. Is It possible to guarantee that an entire set of messages (for example 1 million) we want to log, will be committed only at the end? I would like that, if for example the Producers loose the connection with the brokers and cannot restabilish it, no messages will be seen by the consumers. Is it possible? 回答1: Yes this is possible using Transactions in your producer. You start a

问题 I'm working on a design for a concurrency-safe incremental aggregate rollup system,and track_commit_timestamp (pg_xact_commit_timestamp) sounds perfect. But I've found very little commentary on it generally, and couldn't figure out how it works in detail from the source code. Hopefully, someone knows the answers to one or more of my questions: Is it possible for the commit timestamp feature to produce times out of order? What I'm after is a way to identify records that have been changed since

问题 I use PDO transaction try { DB::$db->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION); DB::$db->beginTransaction(); $db->prepare( insert query ); $db->execute(); $last_insert_id = $db->lastInsertId(); ... ... Multiple concurrent requests are expected on this script. Question: is it possible that lastInsertId() return incorrect value for the user, who actually inserted the row? (by "incorrect value" i mean: id that is inserted by some other user). 回答1: You're safe. The ID you get will

问题 I use PDO transaction try { DB::$db->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION); DB::$db->beginTransaction(); $db->prepare( insert query ); $db->execute(); $last_insert_id = $db->lastInsertId(); ... ... Multiple concurrent requests are expected on this script. Question: is it possible that lastInsertId() return incorrect value for the user, who actually inserted the row? (by "incorrect value" i mean: id that is inserted by some other user). 回答1: You're safe. The ID you get will

问题 So here it is ... // I start transaction $mysqli = new mysqli(...); // Start transaction $mysqli->autocommit(FALSE); here is a select prepared stmt with its own db connection here is an insert prepared stmt with its own db connection here is an slect prepared stmt with the above db conn insert new conn insert new conn insert new conn if every prepared query returs true it will($mysqli->commit()) else $mysqli->rollback I dont know for what reason that transaction will autocommit I've done some