There seems to be lots of information in the mailing list regarding read-only databases and locking when it comes to databases on disk. Both locking and read-only mode seems to be functionality requiring a file on disk. Is it even possible to have locking or read-only mode with in-memory databases?
I am building a cache that will be publicly available. This is done using an SQLite :memory: database for storage. I want to fill a table with data and then make it read-only to prevent any SQL injection attempts. Regular SQL injection mitigation techniques such as parameterization is not possible in this application. In a stand-alone database engine this could have been handled with access control but using SQLite I see no way to prevent SQL Injection in my specific application. A read-only attribute on a table would have solved my problem. Locking could possibly be used to solve this problem but I am unsure. Any ideas? Best regards, Daniel Haglund _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
