A method to avoid file deadlock during concurrent access to the sqlite database

Abstract

The invention discloses a method for avoiding file deadlock during concurrent access to sqlite databases. In the software design stage, one sqlite database on the client side is split into two or more, and each sqlite database corresponds to a certain type of database in the software system. The demand for write operations. Classify all data tables in the software system according to different types of write operations, and place them in different sqlite database files. This can ensure that different types of write operations correspond to different files. When multiple threads in the application software generate write operations at the same time, they are written to different physical disk files, thereby avoiding a The problem that the sqlite database file cannot be concurrently written by multiple threads at the same time.

Description

technical field [0001] The invention belongs to the field of databases, and in particular relates to a method for avoiding file deadlock during concurrent access of SQLite databases in commercial application software. Background technique [0002] As a small relational database commonly used on various operating system platforms, sqlite is widely used in PCs, mobile phones, tablets and other mobile devices. But in actual projects, it is usually necessary to exchange data between the sqlite database and the remote server. As a file database, sqlite does not have the ability to write concurrently by multiple threads, and it does not have the complex transaction and lock mechanism provided by large relational databases (such as oracle, sybase, sqlserver, etc.) to solve this problem. Therefore, in the actual development process of application software, we usually face such a problem: when the client is writing data to the local sqlite database due to user operations, if it is p...

AI Technical Summary

Problems solved by technology

As a file database, sqlite does not have the ability to write concurrently by multiple threads, and it does not have the complex transaction and lock mechanism provided by large relational databases (such as oracle, sybase, sqlserver, etc.) to solve this problem

Therefore, in the actual development process of application software, we usually face such a problem: when the client is writing data to the local sqlite database due to user operations, if it is performing two-way data exchange with the remote server at this time, the Because the sqlite database has been locked, the data exchange operation cannot run normally. This problem occurs more frequently in a multi-threaded environment.

[0015] One: It greatly increases the difficulty of software design and development, which in turn leads to an increase in the cost of software development and a decrease in system stability

Images