transactions

问题 I'm doing some work with EF 4.1 and I'd like to perform a batch update on 3 tables (for the purpose of implementing a soft delete). From doing some quick research it looks like direct SQL queries are best. My implementation is below and I was hoping for some feedback on whether this is best practice. Thanks for the help ... using (var scope = new TransactionScope()) { using (var db = new TimeCatchDb()) { db.Database.ExecuteSqlCommand("UPDATE EmployeeRecords SET Deleted = 1 WHERE NoteTypeId =

问题 We've been trying to implement ACID transactions in Loopback without success. The only examples in the documentation use the 'create' method.We've tried completely overriding the events as well as multiple variations of Operation Hooks. We have only been able to get the create example to work. Core Requirement : We need to be able to start a transaction in the create and update methods for a specific model and then update multiple tables in the transaction (either using Loopback's ORM

问题 My intent Loop through localStorage and put the data into IndexedDB. If certain known errors happen, such as a ConstraintError when a key already exists, I want to ignore those specific errors, so that the transaction is not aborted. Aborting the transaction is the default behaviour when a request triggers an error. The problem I thought that using event.preventDefault() in the requests onerror handler would prevent this from happening. Surprisingly, the event still surfaces in the

问题 In my Java application's DAO layer I have two DAO classes EmployeeDAO and BankDAO . I need to control/handle their database transactions. I use connection pooling to get database connections. EmployeeDAO class: public class EmployeeDAO { String name; String empCode; int age; // Getters & Setters } BankDAO class: public class BankDAO { String bankName; String acNo; String empCode; // Getters & Setters } Let's say I am going to store an Employee and Bank account details related to that employee

问题 We want a simple unit test that runs multiple threads - the idea is that the main thread commits a save to the database, then waits for a secondary thread to pick it up. We're finding that the transaction has to be committed for the second Thread to be able to query the database and find the item. Otherwise, it won't exist. We're trying to accomplish this using an H2 database, Hibernate to manage the access, and the unit test extends AbstractTransactionalJUnit4SpringContextTests . When we try

问题 We want a simple unit test that runs multiple threads - the idea is that the main thread commits a save to the database, then waits for a secondary thread to pick it up. We're finding that the transaction has to be committed for the second Thread to be able to query the database and find the item. Otherwise, it won't exist. We're trying to accomplish this using an H2 database, Hibernate to manage the access, and the unit test extends AbstractTransactionalJUnit4SpringContextTests . When we try

问题 In my application, I need to use pure JDBC together with Guice. However, Guice doesn't provide any built-in support to manage transactions. guice-persist only provides support based on JPA, which I cannot use. so I tried to implement a simple solution to manage transactions with Guice and JDBC. here is the first version: use TransactionHolder to store the transaction per thread. public class JdbcTransactionHolder { private static ThreadLocal<JdbcTransaction> currentTransaction = new

问题 I'm trying to implement the second REST client model presented by Virgil Dobjanschi on this video: http://developer.android.com/videos/index.html#v=xHXn3Kg2IQE This is the high level diagram for the model I'm talking about: I implemented everything as suggested, but I have a complex SQLite database model with lots of tables and I need to use transactions to update my local data with brand new data retrieved from server (step 7 in the picture). Are there any suggestions you could make to help

问题 I'm thinking about making my own IUnitOfWork implementation for an NHibernate persistence layer. It seems that the right way to do this would be to have the ISession and the ITransaction instantiated in the constructor, and then disposed in the destructor or the Dispose() method. Of course, if someone invokes the Save() method, then the ISession would be flushed and the ITransaction would be complete, so after calling Save() , there would not be a valid open transaction to Save() again...

问题 I'm thinking about making my own IUnitOfWork implementation for an NHibernate persistence layer. It seems that the right way to do this would be to have the ISession and the ITransaction instantiated in the constructor, and then disposed in the destructor or the Dispose() method. Of course, if someone invokes the Save() method, then the ISession would be flushed and the ITransaction would be complete, so after calling Save() , there would not be a valid open transaction to Save() again...