Once the SQLite command-line tool is running with the database open. Once done, kill the file or the release the memory and all is back as it was before. Flat files for data storage SQL to improve access to persistent data SQLite for.
If you really have a use-case for a read-only DB, then store the DB file in a read-only location, and before using it from a new connection, first copy the DB file to a temp folder (with read-access), OR serialize it into memory then open that temporary/memory DB and read it to your heart's content.
#Open sqlite file in access driver#
It is assumed that you have already installed and configured a DSN for ODBC driver for SQLite.
#Open sqlite file in access drivers#
Devart ODBC drivers support all modern versions of Access. Even if the DB is opened in read-only mode, the connection must still write locks or WAL logs to simply have read-transactions on the DB file. In Microsoft Access, you can connect to your SQLite data either by importing it or creating a table that links to the data.
There is no way to make an SQLite DB file become "read-only", other than perhaps making the OS / Folder treat it as read-only, but that's like shutting the shop's doors - now nobody can use it. It looks strange that there is no possibility to open db file directly from read only access location/directory. It also does not prevent anyone else from using the shop, they can still use it and some of them might still buy stuff from it. This does not mean that the shop will stop selling stuff, it's still open for business to other people. It's like when you go to a shop and you tell the shopkeeper that you promise to not buy anything while you are inside, and the shopkeeper says Ok, but then leave your wallet/cash/cards outside please, now the shopkeeper knows for a fact you cannot buy anything, but you can look around all you want. It says nothing about any other connection or the DB itself. When you open an SQLite database in read-only mode, it doesn't change the database into some form of "read-only" database, it merely means that you promise (and can be held to the promise) that you will will not try to make changes to the DB from THIS connection you are making. The previous replies are already correct, but it seems you may be missing some basics, which I will try to fill in here.
0 kommentar(er)
