Abstract
Most applications that use sophisticated database management systems, such as Microsoft’s SQL Server, are used by more than one person at a time. The concurrency concerns surrounding shared access to simple data files are often the motivating reason why developers turn to relational database systems to support their applications. Many, but not all, of the concurrency concerns evaporate when an application relies on a relational database for its data store. The concerns that remain usually involve detecting and controlling when an object state is different in memory than in the database. The recipes in this chapter provide an introduction to solving some of the problems typically faced by developers when it comes to detecting concurrency violations and controlling which copy of the object is ultimately persisted in the database.
Keywords
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsAuthor information
Authors and Affiliations
Rights and permissions
Copyright information
© 2013 Brian Driscoll
About this chapter
Cite this chapter
Driscoll, B., Gupta, N., Vettor, R., Hirani, Z., Tenny, L. (2013). Concurrency. In: Entity Framework 6 Recipes. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-5789-9_14
Download citation
DOI: https://doi.org/10.1007/978-1-4302-5789-9_14
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-5788-2
Online ISBN: 978-1-4302-5789-9
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books