This week's book giveaway is in the NodeJS forum. We're giving away four copies of Serverless Applications with Node.js and have Slobodan Stojanovic & Aleksandar Simovic on-line! See this thread for details.
Absolutely there are. There's far too much to be posted in this little box, though. Start reading at Database transaction and follow the relevant-looking links. Whole books could be (and have been) written about the topic, you might benefit from reading one of those books.
posted 7 years ago
Thank you. This is a quote from one of the articels: Of the four ACID properties in a DBMS (Database Management System), the isolation property is the one most often relaxed. When attempting to maintain the highest level of isolation, a DBMS usually acquires locks on data or implements multiversion concurrency control, which may result in a loss of concurrency. This requires adding additional logic for the application to function correctly. and this is exmaple code for Transaction 1 Transaction 2
I guess I have to learn about repeated reads and dirty reads and include the appropriate code in the application to deal with these issues. I found the reading very helpful and I am not done with it yet; but , on the mean time, do you have any suggestions in relation to implementing concurrency control in the application that I might need to be aware of?
posted 7 years ago
Do you think that for the moment; while I implement concurrency code; I could have a single user reading, inserting and updating one table; while the other one reads, inserts and deletes a different one? Would concurrency be an issue if two users are connected and reading, inserting and updating the database at the same time even though they are working on different tables? Does the database management system take care of concurrent access to the database?
If I had asked people what they wanted, they would have said faster horses - Ford. Tiny ad:
global solutions you can do in your home or backyard