Database locking is a varied, evolving, complicated, and technical topic. This paper sheds light on the nature of database locking and how it varies between different platforms. It also discuss the types of application issues that can arise related as a result. It then looks at ways to ferret out these issues and to resolve them before they sneak out the door with your finished product. Armed with this understanding of the enemy and how it relates to your application, you�ll be much better able to avoid disaster.
Die gezeigten Posts sind eventuell nicht akkurat bei Änderungen, die vor Kurzem vorgenommen worden. Wollen Sie jedoch akkurate Posts mit eingeschränkten Sortierungsmöglichkeiten, folgen Sie dem folgenden Link.
J. Bennedssen, und M. Caspersen. Proceedings of the Fourth international Workshop on Computing Education Research, Seite 15--26. New York, NY, USA, ACM, (2008)
E. Bersoff, V. Henderson, und S. Siegel. Proceedings of the software quality assurance workshop on Functional and performance issues, Seite 9--17. New York, NY, USA, ACM, (1978)
S. Bethard, und D. Jurafsky. Proceedings of the 19th ACM international conference on Information and knowledge management, Seite 609--618. New York, NY, USA, ACM, (2010)
C. Bird, D. Pattison, R. D'Souza, V. Filkov, und P. Devanbu. Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering, Seite 24--35. New York, NY, USA, ACM, (2008)