c# - Sqlite: appropriate use of commit -

in server application(written in c#) multiple requests come simultaneously , server both read , write operation on sqlite db.

now problem when server tries insert database @ time of other request reading database transaction.commit() throwing exception database locked, executenonquery() executing successfully. problem committing database.

we committing after every insert , update query. can problem avoid committing once(keep database in memory , commit on application close)? or there other way handle situation.

it seems need implement busy callback or busy timeout, sql lite has lock entire database when writing:

multiple processes can have same database open @ same time. multiple processes can doing select @ same time. 1 process can making changes database @ moment in time, however.

can multiple applications or multiple instances of same application access single database file @ same time?