Oracle, SQL Server, DB2 and all major commercial databases work fine with multiple levels of redo by many different users.
Is SQLite robust enough to do this also or are there limitations on the transaction handling?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
SQLite database is in a file on disc. if you want to do you have to do multiple database writes, put them inside a transaction. Since every write will lock the file(db). SQLite behaves well with large transactions though. I have no solid data compare this with other databases you mentioned but large transactions are handled well in SQLite.